Do I need an active Pdfmonkey connection?

Yes. You must have an ACTIVE connection via RUBE_MANAGE_CONNECTIONS with the pdfmonkey toolkit before executing workflows.

Why must I search tools first?

Tool schemas change frequently. RUBE_SEARCH_TOOLS provides current slugs, required fields, and recommended plans to ensure correct execution.

pdfmonkey-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Pdfmonkey Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pdfmonkey

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Pdfmonkey connection via RUBE_MANAGE_CONNECTIONS with toolkit pdfmonkey
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 pdfmonkey
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: "Pdfmonkey 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 Pdfmonkey task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["pdfmonkey"]
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 Pdfmonkey-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `pdfmonkey`
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/pdfmonkey-automation/SKILL.mdView on GitHub

Overview

This skill lets you automate Pdfmonkey operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows and requires an active Pdfmonkey connection. Setup guides ensure you connect, verify, and execute with schema-compliant arguments.

How This Skill Works

Connect to the Rube MCP server, use RUBE_SEARCH_TOOLS to fetch available Pdfmonkey tool slugs and input schemas, then verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tools via RUBE_MULTI_EXECUTE_TOOL, passing exact schema fields and a memory payload as required.

When to Use It

Automating batch Pdfmonkey document creation from a data source
Updating or applying changes to Pdfmonkey tool schemas before use
Integrating Pdfmonkey workflows into CI/CD pipelines
Generating multiple PDFs (invoices, reports, or contracts) in rapid succession
Validating tool availability and connections before running complex workflows

Quick Start

Step 1: Add the Rube MCP endpoint https://rube.app/mcp as an MCP server in your client
Step 2: Run RUBE_SEARCH_TOOLS and verify Pdfmonkey tool slugs and input schemas are returned
Step 3: Use RUBE_MANAGE_CONNECTIONS to connect to toolkit pdfmonkey, then execute tools with RUBE_MULTI_EXECUTE_TOOL using memory and session_id

Best Practices

Always run RUBE_SEARCH_TOOLS first to retrieve current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results (no hardcoding)
Include memory (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automatically generate weekly invoices from CRM data using a Pdfmonkey tool slug discovered at runtime
Create client-facing PDFs (contracts, quotes) by fetching template fields from Pdfmonkey via Rube MCP
Bulk update and deploy new Pdfmonkey templates after a schema change detected by RUBE_SEARCH_TOOLS
Generate batch project reports as PDFs triggered by a project management system
Produce status PDFs for multiple orders in a single workflow using discovered tool slugs

Frequently Asked Questions

Add this skill to your agents