MULTI-APP TOOLKIT
Build with Motion + n8n.io
- Multi-app
- One MCP session
- 7 actions
- 1 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Motion 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": "motion,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: Motion and n8n.io tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Task:
const result = await mcp.callTool({
name: "motion-create-task",
arguments: {
workspaceId: "Workspace Id",
projectId: "Project Id",
},
})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 [motionTools, n8nIoTools] =
await Promise.all([
pd.components.list({ app: "motion" }),
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=motion" \
-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
Motion
Connected account
n8n.io
Connected account
TOOLS
Motion tools
The Motion tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Task
actionCreate a new task. See the documentationWritev0.0.2 -
Delete Task
actionDelete a specific task by Id. See the documentationWritev0.0.2 -
List Workspace ID Options
actionRetrieves available options for the Workspace ID field.Read-onlyv0.0.1 -
Move Workspace
actionMove a specific task to another workspace. When moving tasks from one workspace to another, the tasks project, status, and label(s) and assignee will all be reset. See the documentationWritev0.0.3 -
Retrieve Schedules
actionGet a list of schedules for your user. See the documentationRead-onlyv0.0.2 -
Retrieve Task
actionRetrieve a specific task by Id. See the documentationRead-onlyv0.0.2 -
Update Task
actionUpdate a specific task. See the documentationWritev0.0.2
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
- motion,n8n_io
- Primary app
- Motion (motion)
- Second app
- n8n.io (n8n_io)
- Authentication
- API key + API key
- Available actions
- 7
- Available triggers
- 1