Pdfless Automation

What This Skill Does

This skill enables users to automate Pdfless operations through the Composio platform using Rube MCP. It is intended for developers and automation specialists who need to incorporate PDF processing tasks into their applications. The skill offers tools for discovering available Pdfless tools, managing connections, and executing specific PDF-related tasks.

When to Use

Generate PDFs from templates. Fill PDF forms programmatically. Add watermarks to PDF documents. Sign PDF files digitally. Convert HTML to PDF. Optimize PDFs for web viewing.

Key Features

Automates Pdfless operations via Rube MCP. Uses Composio's Pdfless 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 Pdfless connection via RUBE_MANAGE_CONNECTIONS with toolkit pdfless 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 pdfless 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: "Pdfless 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 Pdfless task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

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