What prerequisites are needed to use docuseal-automation?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must be available, and an active Docuseal connection via RUBE_MANAGE_CONNECTIONS with the docuseal toolkit is required.

Why should I call RUBE_SEARCH_TOOLS before executing tools?

Tool schemas change over time. Fetching current slugs and input schemas prevents using stale or incorrect arguments.

What should I do if a tool execution fails?

Verify the connection is ACTIVE, ensure you are using the exact schema-compliant arguments from the search results, include the memory field, and retry with a fresh session_id if necessary; also check for pagination and updated tool schemas.

docuseal-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/docuseal-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Docuseal Automation via Rube MCP

Automate Docuseal operations through Composio's Docuseal toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/docuseal

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Docuseal connection via RUBE_MANAGE_CONNECTIONS with toolkit docuseal
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 docuseal
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Docuseal operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Docuseal task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["docuseal"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Docuseal-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `docuseal`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/docuseal-automation/SKILL.mdView on GitHub

Overview

Automate Docuseal operations through Composio's Docuseal toolkit using Rube MCP. Always fetch current tool schemas before running workflows to avoid broken integrations, and ensure an active Docuseal connection to execute tools reliably.

How This Skill Works

The process starts by discovering available Docuseal tools with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas. Next, verify the Docuseal connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, execute the selected tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, schema-compliant arguments, and a memory payload, reusing session IDs as appropriate.

When to Use It

When you need to automate a Docuseal workflow and rely on current tool schemas
When integrating Docuseal operations into an automated pipeline and validating connections beforehand
When updating tool slugs due to schema changes and avoiding hardcoded values
When performing batch or bulk Docuseal tasks via RUBE_REMOTE_WORKBENCH
When reusing a session ID to chain multiple Docuseal steps in a single workflow

Quick Start

Step 1: Verify RUBE MCP connection and fetch current Docuseal tool schemas with RUBE_SEARCH_TOOLS.
Step 2: Manage the Docuseal connection using RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the tool slug, correct arguments, and a memory payload; reuse the session_id as needed.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS reportsACTIVE before executing any tool
Use exact field names and types from the search results to ensure schema compliance
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones for new workflows; handle pagination when listing tools

Example Use Cases

Automate a Docuseal signing workflow by discovering a signing tool with RUBE_SEARCH_TOOLS and executing it via RUBE_MULTI_EXECUTE_TOOL using the provided schema.
Establish a Docuseal connection with RUBE_MANAGE_CONNECTIONS, ensure ACTIVE, then run a batch of contracts using RUBE_REMOTE_WORKBENCH.
In a CI pipeline, validate tool schemas on each run with RUBE_SEARCH_TOOLS, then execute a Docuseal operation with the current slug and memory field.
Migrate from manual Docuseal tasks to automation by building a workflow that reuses a session_id across steps.
Handle tool changes by re-fetching schemas before every workflow to prevent stale tool slugs.

Frequently Asked Questions

Add this skill to your agents