MULTI-APP TOOLKIT
Build with FedEx + 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 FedEx 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": "fedex,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: FedEx and n8n.io tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Shipment:
const result = await mcp.callTool({
name: "fedex-create-shipment",
arguments: {
accountNumber: "Account Number",
shipperStreetLines: ["Shipper Street Lines"],
},
})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 [fedexTools, n8nIoTools] =
await Promise.all([
pd.components.list({ app: "fedex" }),
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=fedex" \
-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
FedEx
Connected account
n8n.io
Connected account
TOOLS
FedEx tools
The FedEx tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Shipment
actionCreate a new shipment. See the documentationWritev0.0.3 -
Track by Reference
actionTracks a package by reference number. See the documentationRead-onlyv0.0.1 -
Track by TCN
actionTracks a package by transportation control number. See the documentationRead-onlyv0.0.1 -
Track by Tracking Number
actionTracks a package by tracking number. See the documentationRead-onlyv0.0.1 -
Track Multi-Piece Shipment
actionTracks a multi-piece shipment. See the documentationRead-onlyv0.0.1 -
Validate Shipment
actionValidate a shipment. See the documentationRead-onlyv0.0.3
Triggers
No FedEx 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
- fedex,n8n_io
- Primary app
- FedEx (fedex)
- Second app
- n8n.io (n8n_io)
- Authentication
- OAuth + API key
- Available actions
- 6
- Available triggers
- 0