Can HumDay connect to Google Fitness?

Yes. HumDay reads Google Fitness's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 13 operations are documented.

Do I need to write code to automate Google Fitness?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Fitness account.

What can HumDay do in Google Fitness?

8 of the 13 documented operations change something in Google Fitness, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Fitness account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Fitness is held behind that approval.

Automate Google Fitness

HumDay reads Google Fitness’s own published API description and derives 13 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Fitness is

The Fitness API for managing users' fitness tracking data.

API host: fitness.googleapis.com

What HumDay can do in Google Fitness

8 documented operations change something in Google Fitness.

POSTCreates a new data source that is unique across all data sources belonging to this user./{userId}/dataSources
POSTAggregates data of a certain type or stream into buckets divided by a given type of boundary./{userId}/dataset:aggregate
DELETEDeletes a session specified by the given session ID./{userId}/sessions/{sessionId}
PUTUpdates or insert a given session./{userId}/sessions/{sessionId}
DELETEDeletes the specified data source./{userId}/dataSources/{dataSourceId}
PUTUpdates the specified data source./{userId}/dataSources/{dataSourceId}
PATCHAdds data points to a dataset./{userId}/dataSources/{dataSourceId}/datasets/{datasetId}
DELETEPerforms an inclusive delete of all data points whose start and end times have any overlap with the time range specified by the dataset ID./{userId}/dataSources/{dataSourceId}/datasets/{datasetId}

What HumDay can read from Google Fitness

These are the operations a schedule or a trigger can watch.

GETLists sessions previously created./{userId}/sessions
GETQueries for user's data point changes for a particular data source./{userId}/dataSources/{dataSourceId}/dataPointChanges
GETReturns the specified data source./{userId}/dataSources/{dataSourceId}
GETReturns a dataset containing all data points whose start and end times overlap with the specified range of the dataset minimum start time and maximum end time./{userId}/dataSources/{dataSourceId}/datasets/{datasetId}
GETLists all data sources that are visible to the developer, using the OAuth scopes provided./{userId}/dataSources

How automating Google Fitness works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Fitness account.
Grant access, then go live. You approve the specific Google Fitness operations it may use — and only those.