MULTI-APP TOOLKIT
Build with n8n.io + Plainly
- Multi-app
- One MCP session
- 6 actions
- 3 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every n8n.io and Plainly 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": "n8n_io,plainly",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: n8n.io and Plainly tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Render Job:
const result = await mcp.callTool({
name: "plainly-create-render-job",
arguments: {
projectId: "Project ID",
templateId: "Template 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 [n8nIoTools, plainlyTools] =
await Promise.all([
pd.components.list({ app: "n8n_io" }),
pd.components.list({ app: "plainly" }),
])
// 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=n8n_io" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=plainly" \
-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
n8n.io
Connected account
Plainly
Connected account
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.
TOOLS
Plainly tools
The Plainly tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Render Job
actionCreates a render job for a video template. See the documentationWritev0.0.2 -
Get Render Status
actionRetrieves the current status of a render job in Plainly. See the documentationRead-onlyv0.0.2 -
List Brand ID Options
actionRetrieves available options for the Brand ID field.Read-onlyv0.0.1 -
List Project ID Options
actionRetrieves available options for the Project ID field.Read-onlyv0.0.1 -
List Render ID Options
actionRetrieves available options for the Render ID field.Read-onlyv0.0.1 -
List Templates
actionFetches a list of available video templates in a project in the user's Plainly account. See the documentationRead-onlyv0.0.2
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
- n8n_io,plainly
- Primary app
- n8n.io (n8n_io)
- Second app
- Plainly (plainly)
- Authentication
- API key + API key
- Available actions
- 6
- Available triggers
- 3