Export Google Fit Daily Steps, Weight and Distance to a Google Sheet

Updated on Tuesday, September 5, 2023

Google Fit Daily Step Export

Google Fit is a great way to keep track of your daily step count without needing to carry a Fitbit or other dedicated tracker. It's not easy to get that data out though, as far as I can tell the only way is Google Takeout which is not made for automation. Luckily there is an API and you can do almost anything with Google Sheets.

If you're looking to export your step count, weight and distance this post has everything you need, just follow the instructions below to get your spreadsheet up and running. This is also a good primer on using OAuth2 with Google Apps Script and should be a decent starting point for a more complex Google Fit integration. If you have any questions or feedback please leave a comment below.

To get started you need a Google Sheet, an apps script project attached to the sheet and a Google API Project that will provide access to the Fitness API. That might sound intimidating but it should only take a few minutes to get everything up and running.

In Google Drive create a new spreadsheet and call it whatever you like. Rename the first tab to 'Metrics'. Enter 'Date' in cell A1, 'Steps' in B1, 'Weight' in C1 and 'Distance' in D1. To grab history as well create another tab called 'History' with the same headers. Next select 'Script editor...' from the Tools menu which will open a new apps script project.

Give the apps script project a name and then select 'Libraries...' from the Resources menu. Next to 'Add a library' enter 1B7FSrk5Zi6L1rSxxTDgDEUsPzlukDsi4KGuTMorsTQHhGBzBkMun4iDF and click Add. This will find the Google OAuth2 library. Choose the most recent version (24 at the time of writing) and click Save. Then select 'Project properties' from the File menu and make a note of the Script ID (a long series of letters and numbers).

Open the Google API Console. Create a new project and name it something like 'Google Fit Sheet'. From the Dashboard click Enabled APIs and services and find and select the Fitness API. Then go to Credentials and create an OAuth Client ID. You'll be asked to create a consent screen, the only field you need to enter is the product name (i.e. 'My Fit App'). Then choose Web Application as the application type. You need to set the name and the authorized redirect URL. The redirect URL is https://script.google.com/macros/d/{SCRIPTID}/usercallback replacing {SCRIPTID} with the actual Script ID you made a note of above. After adding this make a note of the Client ID and Client Secret.

Go back to the apps script project and paste the code below into the Code.gs window:

Right at the top of the code there are spaces to enter the Client ID and Client Secret from the API Console. Enter these and save the project.

Switch back to your Google Sheet and reload. After reloading there will be a Google Fit menu item. First select Authorize... You'll get a screen to authorize the script and then a sidebar with a link. Click the link to authorize the script to access your Google Fit data. You can then close the sidebar and select Get Metrics for Yesterday from the Google Fit menu. You should see a new row added to the spreadsheet with yesterday's date and fitness data.

The final step is to automate pulling in the data. Go back to the apps script project and select Current project's triggers from the Edit menu. Add a trigger to run getMetrics() as a time driven day timer - I recommend between 5 and 6am. You can also click notifications to add an email alert if anything goes wrong, like your Google Fit authorization expiring (in which case you just need to come back and authorize from the Google Fit menu again.

At this point you're all set. Every day the spreadsheet will automatically update with your step count from the day before. You can add charts, moving averages, export to other systems, pull in your weight or BMI, etc. I want to add a seven day moving average step count to this blog somewhere as a semi-public motivational tool... watch this space.

Note that weight will be blank in the spreadsheet for days with no weight data. Google Fit doesn't return the last known weight, only the known value for days where an update was recorded.

If you are looking to extend this sample to other data types then this API explorer page is very helpful for finding data types that the API documentation doesn't list.

A couple of times working on this script I got my authorization in a bad state and started getting a 400 error response from the API. If this happens run your Google Fit app, click the Profile icon at the bottom and then the Settings icon at the top right. Click Manage connected apps and then disconnect the script from Google Fit. Finally run the Reset Settings option from the menu in the sheet and then authorize again.

I updated this post on Jan 21, 2019 to extend the sample to handle weight and distance as well as steps. I also improved the history function to handle many days in one API call rather than a quick hack I added earlier that pulled a day at a time. I'd recommend using the code above rather than anything included in comments below (at least comments before this update).

Add your comment...

More Google Apps Script Projects

(All Code Posts)



Just to update, I got this working.

In the Oauth I did not get an option to select the application type (web application) until after I had configured the consent screen. Ignore what I said about scopes - you don't need to select those at all.

Great resource, thanks. Actually unbelievable that Google doesn't provide this as part of the Google Fit app


Like Alex, I also cannot get past the Oauth part in the cloud console

I've selected the scopes I think I need (auth/fitness.activity.read, auth/fitness.body.read, auth/fitness.location.read) but there is nowhere to add a redirect URL and it doesn't have a client ID or client secret.

It also will not let me publish it without submitting for verification. As I'm the only person who will use it, that seems overkill.

Any idea where to go from here?

Robert Ellison

Alex - it's Credentials now rather then Keys. I've updated the step. If that's not helping please be a little more specific about where you're stuck.


Hi Robert, thanks for your guide, but I am having trouble at the google API console. Has it perhaps changed since you made the guide? Because when i try to create an OAuth Client ID the information is different to what you are saying, and I am not familiar enough with google APIs in order to see what I should do. Please let me know




Does anybody know how to prevent the authorization from expiring?

With "Publishing Status" set to "Testing" in the GCP console, the credentials expire after 7 days. If I publish the app and the status becomes "In Production" (without going though any verification steps), the credentials expire within a few hours.

The 7-day expiry seems to be expected behavior (see "How to add authentication to a Google apps script without it expiring?" on stackoverflow) but I haven't found a way around it without having to go through Google's verification process.


Here's my code for fetching sleep data. Make sure you add the appropriate scope (fitness.sleep.read), and then trigger getSleepData().


// Populate sleep data

function getSleepData() {

const numDaysToGet = 10;

const tabName = 'GFitImportSleep';

const timezone = 'America/Los_Angeles';

getDailySleepData(numDaysToGet, 0, tabName, timezone);


// Format string number of milliseconds using provided timezone and format string

function toDate(millis, tz, format) {

var d = new Date(parseInt(millis));

return Utilities.formatDate(d, tz, format);



Load sleep sessions and overwrite the given tab with the data.

First line of output is a description, second line is headers.


function getDailySleepData(fromDaysAgo, toDaysAgo, tabName, timezone) {

let start = new Date();


start.setDate(start.getDate() - fromDaysAgo);

let end = new Date();


end.setDate(end.getDate() - toDaysAgo);

const url = `https://www.googleapis.com/fitness/v1/users/me/sessions?startTime=${start.toISOString()}&endTime=${end.toISOString()}&activityType=72`;

const fitService = getFitService();

const response = UrlFetchApp.fetch(url, {

headers: {

Authorization: 'Bearer ' + fitService.getAccessToken()


'method' : 'GET',


const json = JSON.parse(response.getContentText());


let ss = SpreadsheetApp.getActiveSpreadsheet();

let sheet = ss.getSheetByName(tabName);

sheet.clear({ formatOnly: false, contentsOnly: true });

sheet.appendRow(["This sheet is generated via Apps Script using the GFit API. Use the 'Google Fit' menu to regenerate manually. If seeing authorization errors, click 'Reset Settings' and then 'Authorize' in that menu."])

sheet.appendRow(["startTimeMillis", "start time", "endTimeMillis", "end time", "end date", "duration (h)", "data"]);

for(var s = 0; s < json.session.length; s++) {

const session = json.session[s];

const duration_m = (session.endTimeMillis - session.startTimeMillis)/(1000 * 60 * 60);



toDate(session.startTimeMillis, timezone, 'h:mm:ss a MM/dd/yy z'),


toDate(session.endTimeMillis, timezone, 'h:mm:ss a MM/dd/yy z'),

toDate(session.endTimeMillis, timezone, 'MM/dd/yy'),






Baran Gulmez

i wanted to add sleep data too but i just couldn't find the documentation of google for below lines anywhere. how can i find sleep data's dataTypeName and dataSourceId ?


"dataTypeName": "derived:com.google.step_count.delta",

"dataSourceId": "derived:com.google.step_count.delta:com.google.android.gms:estimated_steps"



"dataTypeName": "com.google.weight.summary",

"dataSourceId": "derived:com.google.weight:com.google.android.gms:merge_weight"



"dataTypeName": "com.google.distance.delta",

"dataSourceId": "derived:com.google.distance.delta:com.google.android.gms:merge_distance_delta"


Diedrich S

Hi Robert and others interested,

I figured out what the problem was. It was getting the data, but it wasn't being treated correctly. In the function getMetricsForDays, there's a for loop where it looks like there's commands to assign numerical data types. In the case of move minutes, it's an integer value, and I was assigning it a floating point value, fpValue, and it should be intVal, just like the number of steps. After changing this, it worked just fine.



Diedrich S

Hi Robert,

Thanks for your reply. I'm not sure how to check the JSON response, I am not that familiar with Java scripting.

The strange thing is that I get nothing for move minutes. I also don't get any error, either. But, what has changed is that I need to re-authorize the script each day, whereas before adding in the move minutes changes, I didn't need to.

The stackoverflow link I provided in the previous comment claims that it works for that person.

Since I'm not familiar with this type of scripting, I am not sure where to begin debugging it.



Robert Ellison

Hi Diedrich, I'd start by examining the JSON response. Are you getting anything at all for move minutes? Maybe it's some small difference in how it needs to be parsed.

Add Comment

All comments are moderated. Your email address is used to display a Gravatar and optionally for notification of new comments and to sign up for the newsletter.



Average Server Response Time in Azure Metrics