Api2pdf Automation via Rube MCP

SkillSearch

This skill gives your AI the ability to create PDFs using Api2pdf. Once added, your AI can convert web pages, HTML, and documents into PDF files for you, handling the conversion steps from start to finish.

Available today. Use it from your connected AI after setup.

After adding the skill, ask your AI to look up the available Api2pdf actions, then have it convert a web page or document into a PDF as a first test.

Then ask your AI: use the Api2pdf Automation via Rube MCP skill

What your AI can do with it

  • Convert web pages into PDF files
  • Turn HTML into PDF files
  • Convert documents into PDF files
  • Run Api2pdf conversion tasks automatically
  • Check the current conversion options before each task

What this skill tells your AI

The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/api2pdf-automation/SKILL.md and read by ahel’s review.

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

Toolkit docs: composio.dev/toolkits/api2pdf

Prerequisites

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

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Api2pdf 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 Api2pdf task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Api2pdf-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit api2pdf
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Signals

GitHub stars
16k
Forks
2k
Last commit
Jul 2026

Others that do the same job

Advanced
Catalog kind
skill
Gateway key
api2pdf-automation
Source
github.com/composio-community/awesome-codex-skills