MULTI-APP TOOLKIT
Build with Fitbit + n8n.io
- Multi-app
- One MCP session
- 6 actions
- 0 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Fitbit and n8n.io tool at once — connect once, list tools, and call them like any single-app session.
// 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,n8n_io",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Fitbit and n8n.io tools arrive
// together, each keyed by its own app's slug.
// e.g. run Get Activity Summary:
const result = await mcp.callTool({
name: "fitbit-get-activity-summary",
arguments: {
date: "Date",
},
})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 externalUserId = "{external_user_id}" // any stable ID for this user in your system
const [fitbitTools, n8nIoTools] =
await Promise.all([
pd.components.list({ app: "fitbit" }),
pd.components.list({ app: "n8n_io" }),
])
// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=fitbit" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=n8n_io" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
# Connect both accounts to the same external_user_id, then
# configure and invoke either app's tools on that user's behalf.ARCHITECTURE
One user, two connected accounts
Your user connects each account once, under whatever ID they already have in your product. The two stay independent — either can be revoked on its own — and your code reaches both through that one user.
Your product
external_user_id
{external_user_id}Pipedream Connect
Managed identity
Auth · tools · routing
Fitbit
Connected account
n8n.io
Connected account
TOOLS
Fitbit tools
The Fitbit tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
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
Triggers
No Fitbit triggers are available yet.
TOOLS
n8n.io tools
The n8n.io tools this pairing puts in reach, each one running on your user's own connected account.
Actions
No n8n.io actions are available yet.
Triggers
No n8n.io triggers are available yet.
MULTI-APP
Works with more apps
The combinations customers connect alongside these two — nothing here is limited to a pair.
REFERENCE
Toolkit details
- x-pd-app-slug
- fitbit,n8n_io
- Primary app
- Fitbit (fitbit)
- Second app
- n8n.io (n8n_io)
- Authentication
- OAuth + API key
- Available actions
- 6
- Available triggers
- 0