Log weight to Google Health when Oura Ring records a new sleep session
How this automation works
Log new Fitbit weight entries to Google Health to keep your records in sync. When you log a weight in the Fitbit app or with the Aria scale, this Applet forwards the same measurement to Google Health. This is useful for consolidating weight history across Fitbit and Google Health for tracking progress or sharing with healthcare providers.
If
Trigger ingredients
BMI
Weight
WeightUnit
Date
Then
Action fields
weight
weight_unit
Services used in this Applet
You might also like...
-
-
-
Log weight to Google Health when a scene is activated in Google Assistant
-
-
Log weight to Google Health when Android Activity detects you stop running
-
Related services
Create your own Fitbit and Google Health workflow
Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.
28 triggers, queries, and actions
Daily activity summary
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time your Fitbit tracker syncs for the first time today and your previous day's stats are available.
Daily activity summary
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires once a day when your previous day's activity stats are available in Google Health.
Daily calorie burn goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when you achieve your daily calorie burn goal.
Daily distance goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily distance goal.
Daily floors climbed goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.
Daily goal not achieved by __:__
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you do not achieve a daily goal you choose at the time you specify. NOTE: Updated on the first Fitbit tracker sync after the time you specify.
Daily step goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily step goal.
Daily very active minutes goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily very active minutes goal.
New exercise logged
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time a new exercise session is logged in Google Health.
New sleep logged
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time your Fitbit logs new sleep.
New sleep logged
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time new sleep is logged in Google Health.
New weight logged
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you log your weight in the Fitbit app or with the Aria scale.
History of achieved very active minutes goals
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of events when you achieved your very active minute goals.
History of Daily Activity Summaries
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of Daily Activity Summary events from your Fitbit.
History of daily calorie burn goal achieved
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily calorie burn goal.
History of daily floors climbed goal achieved
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.
History of daily goal not being achieved by __:__
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you did not achieve a daily goal you chose by the time you specified. NOTE: Updated on the first Fitbit tracker sync after the time you specified.
History of daily step goal achieved
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily step goal.
History of Sleep duration above threshold
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of events when you logged sleep above the target hours you specified. Note: this query will only return future events after this Applet is created.
History of sleep duration below
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you log sleep below the target hours you specify. Note: this query will only return future events after this Applet is created.
History of sleep logged
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when your Fitbit logs new sleep.
History of weight logged
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you logged your weight in the Fitbit app or with the Aria scale.
History of when the daily distance goal was achieved
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you have achieved your daily distance goal.
Log your weight
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will log a new weight measurement to Fitbit.
Log your weight
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will log a new weight measurement to Google Health.
Daily activity summary
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time your Fitbit tracker syncs for the first time today and your previous day's stats are available.
Daily activity summary
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires once a day when your previous day's activity stats are available in Google Health.
Daily calorie burn goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when you achieve your daily calorie burn goal.
Daily distance goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily distance goal.
Daily floors climbed goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.
Daily goal not achieved by __:__
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you do not achieve a daily goal you choose at the time you specify. NOTE: Updated on the first Fitbit tracker sync after the time you specify.
Daily step goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily step goal.
Daily very active minutes goal achieved
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily very active minutes goal.
History of achieved very active minutes goals
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of events when you achieved your very active minute goals.
History of Daily Activity Summaries
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of Daily Activity Summary events from your Fitbit.
History of daily calorie burn goal achieved
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily calorie burn goal.
History of daily floors climbed goal achieved
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.
Build an automation in seconds!
If
Select a trigger the automation will use
Then
Select an action the automation will perform
You can add delays, queries, and more actions in the chat.
More on Fitbit and Google Health
About Fitbit
Fitbit designs products to track everyday health and fitness, empowering and inspiring people to lead healthier, more active lives. Turn on Applets to track your fitness and sleep goals, build healthier habits, and sync your fitness data to hundreds of other services.
Fitbit designs products to track everyday health and fitness, empowering and inspiring people to lead healthier, more active lives. Turn on Applets to track your fitness and sleep goals, build healthier habits, and sync your fitness data to hundreds of other services.
About Google Health
Google Health brings together the health and fitness data recorded by your Fitbit trackers, Pixel Watch, and the Google Health app — activity, sleep, weight, and exercise. Turn on Applets to log your stats automatically and put your health data to work.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Google Health brings together the health and fitness data recorded by your Fitbit trackers, Pixel Watch, and the Google Health app — activity, sleep, weight, and exercise. Turn on Applets to log your stats automatically and put your health data to work.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.