What prerequisites are required to use callpage-automation?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available and an Active Callpage connection via RUBE_MANAGE_CONNECTIONS for the callpage toolkit.

Should I hardcode tool slugs?

No. Always search tools first to obtain current slugs and input schemas and avoid breaking changes.

How do I run a multi-step Callpage workflow safely?

Discover tools with RUBE_SEARCH_TOOLS, verify ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute tools with RUBE_MULTI_EXECUTE_TOOL using memory and a persistent session_id.

callpage-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Callpage Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/callpage

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Callpage operations by interfacing with Composio's Callpage toolkit through Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before any execution to prevent hardcoding slugs. Setup, discovery, connection checks, and tool execution are covered to enable reliable workflows.

How This Skill Works

First, you discover available Callpage tools using RUBE_SEARCH_TOOLS to obtain slugs and input schemas. Then you ensure an ACTIVE connection via RUBE_MANAGE_CONNECTIONS to the callpage toolkit, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the schema compliant arguments, including memory and session_id.

When to Use It

To start a Callpage automation, first discover tools with RUBE_SEARCH_TOOLS and select a slug based on the task.
When setting up a new integration, verify the Callpage connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running workflows.
Before executing any action, rely on the discovered tool slug and input schemas to avoid hardcoding changes.
For multi-step workflows, reuse a session_id across steps to maintain continuity and state.
If tool schemas change or responses paginate, re-run RUBE_SEARCH_TOOLS to refresh slugs and arguments.

Quick Start

Step 1: Discover Tools with RUBE_SEARCH_TOOLS for Callpage operations.
Step 2: Check Connection with RUBE_MANAGE_CONNECTIONS for the callpage toolkit and ensure status is ACTIVE.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, schema compliant arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before starting any workflow to get current tool schemas.
Verify that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the search results instead of hardcoded values.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session_id within a workflow for continuity and generate new ones for new tasks.

Example Use Cases

Discover Callpage operations, select a tool slug from search results, and execute a simple task in a single session.
Establish a Callpage connection with the toolkit and queue a call using a discovered tool slug.
Run multiple Callpage actions in one session by performing sequential RUBE_MULTI_EXECUTE_TOOL calls with the same session_id.
Detect updated tool schemas, re-search tools, and adjust arguments accordingly before execution.
Maintain memory state across steps when performing bulk Callpage operations to ensure consistent results.

Frequently Asked Questions

Add this skill to your agents