DocuSign Automation via Rube MCP
Automate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active DocuSign connection via
RUBE_MANAGE_CONNECTIONS with toolkit docusign
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit docusign
- If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Browse and Select Templates
When to use: User wants to find available document templates for sending
Tool sequence:
DOCUSIGN_LIST_ALL_TEMPLATES - List all available templates [Required]
DOCUSIGN_GET_TEMPLATE - Get detailed template information [Optional]
Key parameters:
- For listing: Optional search/filter parameters
- For details:
templateId (from list results)
- Response includes template
templateId, name, description, roles, and fields
Pitfalls:
- Template IDs are GUIDs (e.g., '12345678-abcd-1234-efgh-123456789012')
- Templates define recipient roles with signing tabs; understand roles before creating envelopes
- Large template libraries require pagination; check for continuation tokens
- Template access depends on account permissions
2. Create and Send Envelopes from Templates
When to use: User wants to send documents for signature using a pre-built template
Tool sequence:
DOCUSIGN_LIST_ALL_TEMPLATES - Find the template to use [Prerequisite]
DOCUSIGN_GET_TEMPLATE - Review template roles and fields [Optional]
DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE - Create the envelope [Required]
DOCUSIGN_SEND_ENVELOPE - Send the envelope for signing [Required]
Key parameters:
- For CREATE_ENVELOPE_FROM_TEMPLATE:
templateId: Template to use
templateRoles: Array of role assignments with roleName, name, email
status: 'created' (draft) or 'sent' (send immediately)
emailSubject: Custom subject line for the signing email
emailBlurb: Custom message in the signing email
- For SEND_ENVELOPE:
envelopeId: Envelope ID from creation response
Pitfalls:
templateRoles must match the role names defined in the template exactly (case-sensitive)
- Setting
status to 'sent' during creation sends immediately; use 'created' for drafts
- If status is 'sent' at creation, no need to call SEND_ENVELOPE separately
- Each role requires at minimum
roleName, name, and email
emailSubject overrides the template's default email subject
3. Monitor Envelope Status
When to use: User wants to check the status of sent envelopes or track signing progress
Tool sequence:
DOCUSIGN_GET_ENVELOPE - Get envelope details and status [Required]
Key parameters:
envelopeId: Envelope identifier (GUID)
- Response includes
status, recipients, sentDateTime, completedDateTime
Pitfalls:
- Envelope statuses: 'created', 'sent', 'delivered', 'signed', 'completed', 'declined', 'voided'
- 'delivered' means the email was opened, not that the document was signed
- 'completed' means all recipients have signed
- Recipients array shows individual signing status per recipient
- Envelope IDs are GUIDs; always resolve from creation or search results
4. Add Templates to Existing Envelopes
When to use: User wants to add additional documents or templates to an existing envelope
Tool sequence:
DOCUSIGN_GET_ENVELOPE - Verify envelope exists and is in draft state [Prerequisite]
DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE - Add template to envelope [Required]
Key parameters:
envelopeId: Target envelope ID
documentId: Document ID within the envelope
templateId: Template to add
Pitfalls:
- Envelope must be in 'created' (draft) status to add templates
- Cannot add templates to already-sent envelopes
- Document IDs are sequential within an envelope (starting from '1')
- Adding a template merges its fields and roles into the existing envelope
5. Manage Envelope Lifecycle
When to use: User wants to send, void, or manage draft envelopes
Tool sequence:
DOCUSIGN_GET_ENVELOPE - Check current envelope status [Prerequisite]
DOCUSIGN_SEND_ENVELOPE - Send a draft envelope [Optional]
Key parameters:
envelopeId: Envelope to manage
- For sending: envelope must be in 'created' status with all required recipients
Pitfalls:
- Only 'created' (draft) envelopes can be sent
- Sent envelopes cannot be unsent; they can only be voided
- Voiding an envelope notifies all recipients
- All required recipients must have valid email address
1---2name: docusign-automation3description: DocuSign Automation via Rube MCP4---567# DocuSign Automation via Rube MCP89Automate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.1011## Prerequisites1213- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)14- Active DocuSign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docusign`15- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas1617## Setup1819**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2021221. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds232. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docusign`243. If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth254. Confirm connection status shows ACTIVE before running any workflows2627## Core Workflows2829### 1. Browse and Select Templates3031**When to use**: User wants to find available document templates for sending3233**Tool sequence**:341. `DOCUSIGN_LIST_ALL_TEMPLATES` - List all available templates [Required]352. `DOCUSIGN_GET_TEMPLATE` - Get detailed template information [Optional]3637**Key parameters**:38- For listing: Optional search/filter parameters39- For details: `templateId` (from list results)40- Response includes template `templateId`, `name`, `description`, roles, and fields4142**Pitfalls**:43- Template IDs are GUIDs (e.g., '12345678-abcd-1234-efgh-123456789012')44- Templates define recipient roles with signing tabs; understand roles before creating envelopes45- Large template libraries require pagination; check for continuation tokens46- Template access depends on account permissions4748### 2. Create and Send Envelopes from Templates4950**When to use**: User wants to send documents for signature using a pre-built template5152**Tool sequence**:531. `DOCUSIGN_LIST_ALL_TEMPLATES` - Find the template to use [Prerequisite]542. `DOCUSIGN_GET_TEMPLATE` - Review template roles and fields [Optional]553. `DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE` - Create the envelope [Required]564. `DOCUSIGN_SEND_ENVELOPE` - Send the envelope for signing [Required]5758**Key parameters**:59- For CREATE_ENVELOPE_FROM_TEMPLATE:60 - `templateId`: Template to use61 - `templateRoles`: Array of role assignments with `roleName`, `name`, `email`62 - `status`: 'created' (draft) or 'sent' (send immediately)63 - `emailSubject`: Custom subject line for the signing email64 - `emailBlurb`: Custom message in the signing email65- For SEND_ENVELOPE:66 - `envelopeId`: Envelope ID from creation response6768**Pitfalls**:69- `templateRoles` must match the role names defined in the template exactly (case-sensitive)70- Setting `status` to 'sent' during creation sends immediately; use 'created' for drafts71- If status is 'sent' at creation, no need to call SEND_ENVELOPE separately72- Each role requires at minimum `roleName`, `name`, and `email`73- `emailSubject` overrides the template's default email subject7475### 3. Monitor Envelope Status7677**When to use**: User wants to check the status of sent envelopes or track signing progress7879**Tool sequence**:801. `DOCUSIGN_GET_ENVELOPE` - Get envelope details and status [Required]8182**Key parameters**:83- `envelopeId`: Envelope identifier (GUID)84- Response includes `status`, `recipients`, `sentDateTime`, `completedDateTime`8586**Pitfalls**:87- Envelope statuses: 'created', 'sent', 'delivered', 'signed', 'completed', 'declined', 'voided'88- 'delivered' means the email was opened, not that the document was signed89- 'completed' means all recipients have signed90- Recipients array shows individual signing status per recipient91- Envelope IDs are GUIDs; always resolve from creation or search results9293### 4. Add Templates to Existing Envelopes9495**When to use**: User wants to add additional documents or templates to an existing envelope9697**Tool sequence**:981. `DOCUSIGN_GET_ENVELOPE` - Verify envelope exists and is in draft state [Prerequisite]992. `DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE` - Add template to envelope [Required]100101**Key parameters**:102- `envelopeId`: Target envelope ID103- `documentId`: Document ID within the envelope104- `templateId`: Template to add105106**Pitfalls**:107- Envelope must be in 'created' (draft) status to add templates108- Cannot add templates to already-sent envelopes109- Document IDs are sequential within an envelope (starting from '1')110- Adding a template merges its fields and roles into the existing envelope111112### 5. Manage Envelope Lifecycle113114**When to use**: User wants to send, void, or manage draft envelopes115116**Tool sequence**:1171. `DOCUSIGN_GET_ENVELOPE` - Check current envelope status [Prerequisite]1182. `DOCUSIGN_SEND_ENVELOPE` - Send a draft envelope [Optional]119120**Key parameters**:121- `envelopeId`: Envelope to manage122- For sending: envelope must be in 'created' status with all required recipients123124**Pitfalls**:125- Only 'created' (draft) envelopes can be sent126- Sent envelopes cannot be unsent; they can only be voided127- Voiding an envelope notifies all recipients128- All required recipients must have valid email address