Pdf4me Automation

What This Skill Does

This skill allows users to automate PDF4me operations through the Composio platform using Rube MCP. It is designed for developers and automation engineers who need to integrate PDF manipulation tasks into their workflows. The skill provides tools for discovering available PDF4me tools, managing connections, and executing specific PDF tasks.

When to Use

Convert documents to PDF format. Merge multiple PDF files into one. Split a PDF file into individual pages. Compress PDF files to reduce size. Extract text from PDF documents. Secure PDF files with passwords.

Key Features

Automates PDF4me operations via Rube MCP. Uses Composio's PDF4me toolkit. Discovers tools dynamically using RUBE_SEARCH_TOOLS. Manages connections using RUBE_MANAGE_CONNECTIONS. Executes tools with RUBE_MULTI_EXECUTE_TOOL. Provides documentation for setup and usage.

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["pdf4me"] 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