CONNECT APP
Build with Fitbit
Smart Home Automation
- OAuth
MCP
Give your agent Fitbit tools
Every Fitbit action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Fitbit account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "fitbit",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Get Activity Summary:
const result = await mcp.callTool({
name: "fitbit-get-activity-summary",
arguments: {
date: "Date",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "fitbit",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Get Activity Summary:
result = await session.call_tool("fitbit-get-activity-summary", {
"date": "Date",
})API PROXY
Call the Fitbit API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Fitbit API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.fitbit.com/1/user/-/profile.json",
})
// Any allowed Fitbit endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.fitbit.com/1/user/-/profile.json
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZml0Yml0LmNvbS8xL3VzZXIvLS9wcm9maWxlLmpzb24?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Fitbit actions from your backend
Connect a user's Fitbit account once, then run Get Activity Summary on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "fitbit-get-activity-summary",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
fitbit: { authProvisionId: "apn_xxxxxxx" },
date: "Date",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="fitbit-get-activity-summary",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"fitbit": {"authProvisionId": "apn_xxxxxxx"},
"date": "Date",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "fitbit-get-activity-summary",
"configured_props": {
"fitbit": { "authProvisionId": "apn_xxxxxxx" },
"date": "Date"
}
}'TOOLS
Fitbit actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Get Activity Summary
actionGet a daily activity summary including calories, distance, and active minutes. See the documentationRead-onlyv0.0.2 -
Get Body Weight and BMI Logs
actionGets body weight and BMI log entries for a given date. See the docsRead-onlyv0.0.1 -
Get Daily Step Count
actionGets the daily step count for a specific date. See the docsRead-onlyv0.0.1 -
Get Heart Rate
actionGets the heart rate intraday time series data on a specific date range for a 24 hour period. See the documentationRead-onlyv0.0.2 -
Get Nutrition and Water Logs
actionGet nutrition and water logs for a date, including food entries, meals, water intake, and daily summaries. See the Fitbit Web API documentationRead-onlyv0.0.1 -
Get Sleep Data
actionGet sleep data for a date, including duration, stages, and sleep score when available. See the Fitbit Web API documentationRead-onlyv0.0.1
No Fitbit triggers are available yet.
MULTI-APP
Use Fitbit with other popular apps
Most products don't stop at one integration. Pair Fitbit with the other apps your users rely on, and ship use cases that span both.
- App slug
- fitbit
- Authentication
- OAuth
- Categories
- Smart Home Automation
- Actions
- 6
- Triggers
- 0
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Fitbit OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- activity
- heartrate
- location
- nutrition
- settings
- sleep
- social
- weight
- temperature