Automate DocuSign Document Signing

This skill automates DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP (https://rube.app/mcp, no API keys needed). Prerequisites: Rube MCP connected with RUBE_SEARCH_TOOLS available, an active DocuSign connection via RUBE_MANAGE_CONNECTIONS with toolkit docusign (completed via the returned OAuth link if not yet ACTIVE), and always calling RUBE_SEARCH_TOOLS first for current tool schemas.

Its core workflows: browsing and selecting templates (DOCUSIGN_LIST_ALL_TEMPLATES with optional filters, then DOCUSIGN_GET_TEMPLATE for details including defined recipient roles and signing fields) - noting template IDs are GUIDs and large libraries need pagination via continuation tokens; creating and sending envelopes from templates (find the template, review its roles, DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE with templateRoles mapping each defined role to a real recipient's name/email, a status of 'created' for drafts or 'sent' to send immediately, plus custom emailSubject/emailBlurb, then DOCUSIGN_SEND_ENVELOPE if not already sent) - noting templateRoles role names must match the template's defined roles exactly (case-sensitive) and every required role needs at least roleName/name/email; monitoring envelope status (DOCUSIGN_GET_ENVELOPE returning status, recipients, sent/completed timestamps) - noting 'delivered' only means the email was opened, not signed, while 'completed' means every recipient has signed, and the recipients array shows per-recipient signing progress; adding templates to existing draft envelopes (DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE) - only possible while the envelope is still in 'created' status, with document IDs sequential starting from '1'; and managing envelope lifecycle (sending or voiding drafts) - noting only draft envelopes can be sent, sent envelopes can only be voided (not unsent), and voiding notifies all recipients.

Common patterns cover ID resolution (list templates, find by name, extract the GUID templateId), envelope tracking (store the envelopeId from creation, poll DOCUSIGN_GET_ENVELOPE periodically, check recipient-level status), and template role mapping (get the template's defined roles, map each to a real recipient with an exact-matching roleName, and include all required roles in the templateRoles array).

Known pitfalls: template role names are case-sensitive and missing role assignments fail envelope creation; envelope status transitions are one-way and 'delivered' does not mean signed; all DocuSign IDs (templates, envelopes) are GUIDs that must be resolved via list/search rather than hardcoded; DocuSign enforces per-account rate limits requiring throttled bulk envelope creation and reasonable polling intervals (30-60 seconds); and response data may be nested under a data key with recipient info nested inside the envelope response, requiring defensive parsing.

created (draft) -> sent -> delivered -> signed -> completed
                       \-> declined
                       \-> voided (by sender)

Use this skill when browsing templates, creating and sending envelopes from templates, monitoring envelope/signing status, adding templates to draft envelopes, or managing envelope lifecycle (send/void) in DocuSign through Rube MCP.

Inputs: a DocuSign operation request (template lookup, envelope creation/sending, status check, or lifecycle management) with the relevant template/envelope GUIDs and recipient role mappings.

Outputs: created/sent envelopes with correctly mapped signer roles, envelope status and per-recipient signing progress, and updated draft envelopes with added templates.

Rube MCP (https://rube.app/mcp), Composio's DocuSign toolkit (DOCUSIGN_LIST_ALL_TEMPLATES, DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE, DOCUSIGN_SEND_ENVELOPE, DOCUSIGN_GET_ENVELOPE, DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE), DocuSign OAuth.

Teams automating DocuSign e-signature workflows - sending documents for signature, tracking signing progress, and managing envelope lifecycle - via Rube MCP.