What is required to start automating Callerapi tasks?

You need a connected Rube MCP, an active Callerapi connection, and the habit of searching for current tool schemas with RUBE_SEARCH_TOOLS first.

How do I ensure tool schemas stay up to date?

Always call RUBE_SEARCH_TOOLS before execution to obtain the latest tool slugs and input fields; avoid hardcoding.

What should I do if the connection is not ACTIVE?

Follow the auth flow provided by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check for ACTIVE status before running workflows.

callerapi-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Callerapi Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/callerapi

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Callerapi operations through Composio's Callerapi toolkit using Rube MCP. It emphasizes searching for current tool schemas before each run to ensure inputs stay up-to-date. This approach prevents hardcoding slugs and promotes reliable, schema-compliant automation.

How This Skill Works

The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to fetch current tool schemas. Next, it verifies the Callerapi connection via RUBE_MANAGE_CONNECTIONS and ensures the status is ACTIVE. Finally, it executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the schema-compliant arguments and a memory payload within the same session.

When to Use It

You need to automate a Callerapi task and want to pull the latest tool schemas first
Tool slugs or input fields change and hardcoding would break the workflow
You must verify an active Callerapi connection before running workflows
Performing bulk operations or chained steps via RUBE_REMOTE_WORKBENCH or multi-tool execution
Migrating from one workflow to a new Callerapi task while reusing a session

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLs responds
Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkit 'callerapi' and authenticate if prompted
Step 3: Use RUBE_SEARCH_TOOLS to discover a relevant tool, then call RUBE_MULTI_EXECUTE_TOOL with the tool slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools
Use exact field names and types from search results; avoid hardcoding slugs
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination tokens to complete tasks

Example Use Cases

Discover available Callerapi tools with RUBE_SEARCH_TOOLS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the returned slug and input schema
Set up a Callerapi connection by running RUBE_MANAGE_CONNECTIONS with toolkit 'callerapi' and authenticate if required
Handle paginated tool results by continuing fetches until no tokens remain, then proceed to execution
Run a multi-step workflow that reuses a session_id across steps and updates memory between actions
Bulk-operate Callerapi tasks through RUBE_REMOTE_WORKBENCH invoking run_composio_tool() on discovered tools

Frequently Asked Questions

Add this skill to your agents