Docusign ACTION
Create Envelope
Create 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 documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Docusign account once, then configure and run Create Envelope from your backend or agent.
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 result = await pd.actions.run({
id: "docusign-create-envelope",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
docusign: { authProvisionId: "apn_xxxxxxx" },
account: "Account",
envelopeDefinitionJson: "Envelope Definition JSON",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "docusign-create-envelope",
"configured_props": {
"docusign": { "authProvisionId": "apn_xxxxxxx" },
"account": "Account",
"envelopeDefinitionJson": "Envelope Definition JSON"
}
}'// 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",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "docusign-create-envelope",
arguments: {
account: "Account",
envelopeDefinitionJson: "Envelope Definition JSON",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
account Account | string | Your DocuSign account. Leave blank to automatically use your default account, or provide an Account ID (you can use List Accounts to retrieve available accounts). Optional Dynamic |
envelopeDefinitionJson Envelope Definition JSON | string | A full DocuSign envelope definition JSON object. Example: {"emailSubject":"Please sign","status":"sent","documents":[...],"recipients":{"signers":[...]}}. Required |
status Status Override | string | Optional envelope status override. Use created to save as a draft or sent to send immediately. Optional |
mergeRolesOnDraft Merge Roles On Draft | boolean | When creating a draft from multiple templates, merge template roles and remove empty recipients. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- docusign-create-envelope
- Version
- 0.0.3
- App
- Docusign
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗