Skip to content
Skillpedia
Automations48k · #2872

docusign-automation

Helps your agent automate DocuSign tasks. It can manage templates, envelopes, and signatures, making document handling easier.

What it does

This tool automates tasks in DocuSign, like finding document templates, sending contracts for signature, and checking their progress. It helps manage your electronic document lifecycle.

When to use it

  • ✓When you need to find a specific document template in DocuSign.
  • ✓When you want to send a contract to multiple people for signing using a template.
  • ✓When you need to check if a document has been signed or what its status is.

Example of what to ask your AI

“I want to send the rental agreement using the 'Standard Contract' template to John Smith (john@email.com) and Jane Doe (jane@email.com).”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/docusign-automation/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/docusign-automation/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool connects to DocuSign via a system called Rube MCP. It uses specific commands to list templates, create documents from these templates, send them for signature, and check their status.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill docusign-automation

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/docusign-automation/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit docusign
  3. If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth
  4. 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:

  1. DOCUSIGN_LIST_ALL_TEMPLATES - List all available templates [Required]
  2. 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:

  1. DOCUSIGN_LIST_ALL_TEMPLATES - Find the template to use [Prerequisite]
  2. DOCUSIGN_GET_TEMPLATE - Review template roles and fields [Optional]
  3. DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE - Create the envelope [Required]
  4. 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:

  1. 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:

  1. DOCUSIGN_GET_ENVELOPE - Verify envelope exists and is in draft state [Prerequisite]
  2. 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

…

FAQ

What are 'templates'?

Templates are document models you can reuse. They come with the necessary fields to fill in and signature areas.

What is an 'envelope'?

An envelope is the 'package' containing the document you send for signature. It includes the document itself, who needs to sign, and instructions.

How do I know if the document was signed?

The tool can check the envelope's status. It can be 'created', 'sent', 'delivered', 'signed', or 'completed'. 'Completed' means everyone has signed.

Details

Original description by the author

Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#2872
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills