MULTI-APP TOOLKIT
Build with Docusign + LinkedIn
- Multi-app
- One MCP session
- 35 actions
- 3 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Docusign and LinkedIn 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": "docusign,linkedin",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Docusign and LinkedIn tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Draft:
const result = await mcp.callTool({
name: "docusign-create-draft",
arguments: {
account: "Account",
template: "Template",
},
})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 [docusignTools, linkedinTools] =
await Promise.all([
pd.components.list({ app: "docusign" }),
pd.components.list({ app: "linkedin" }),
])
// 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=docusign" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=linkedin" \
-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
Docusign
Connected account
Connected account
TOOLS
Docusign tools
The Docusign tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 13
-
Create Draft
actionCreate and send an envelope, or create a draft envelope. See the documentation hereWritev0.0.6 -
Create Envelope
actionCreate a DocuSign envelope from a full envelope definition JSON payload. Use this for advanced cases such as multiple documents, multiple recipients, composite templates, custom tabs, or eventNotification webhooks. For a simpler single-document flow, use Create Envelope From File. See the documentationWritev0.0.3 -
Create Envelope From File
actionCreate and optionally send a single-document DocuSign envelope from a file path or URL. This action places a SignHere tab by anchor text, such as/sn1/, in the uploaded document. Set Client User ID when you need embedded signing, then use Create Recipient View with the same value. See the documentationWritev0.0.4 -
Create Recipient View
actionCreate an embedded signing URL for a selected envelope recipient. The recipient must have been created with aclientUserId. See the documentationWritev0.0.3 -
Create Signature Request
actionCreates a signature request from a template See the docs hereWritev0.1.6 -
Download Documents
actionDownload the documents of an envelope to the /tmp directory. See the documentation hereRead-onlyv0.0.5 -
Get Envelope
actionGet details for a DocuSign envelope by ID. Use List Envelopes first if you need to find an envelope ID. See the documentationRead-onlyv0.0.3 -
List Accounts
actionList the DocuSign accounts available to the connected user. Use this to find the Account ID required by other actions when the connected user belongs to more than one account. See the documentationRead-onlyv0.0.2
TOOLS
LinkedIn tools
The LinkedIn tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 22
-
Create a Simple Post (Organization)
actionCreate post on LinkedIn using text, URL or article. See the documentation for more informationWritev0.0.13 -
Create a Simple Post (User)
actionCreate post on LinkedIn using text, URL or article. See the documentation for more informationWritev0.0.13 -
Create Comment
actionCreate a comment on a share or user generated content post. See the docs hereWritev0.1.13 -
Create Image Post (Organization)
actionCreate an image post on LinkedIn. See the documentationWritev1.0.9 -
Create Image Post (User)
actionCreate an image post on LinkedIn. See the documentationWritev1.0.9 -
Create Like On Share
actionCreates a like on a share. See the docs hereWritev0.1.13 -
Delete Post
actionRemoves a post from user's wall. See the documentation for more informationWritev0.0.13 -
Fetch Ad Account
actionFetches an individual adAccount given its id. See the docs hereWritev0.1.13
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
- docusign,linkedin
- Primary app
- Docusign (docusign)
- Second app
- LinkedIn (linkedin)
- Authentication
- OAuth + OAuth
- Available actions
- 35
- Available triggers
- 3