$ ~/registry/skill/composiohq-composio-skills-callingly-automation

SKILL

callingly-automation

Automate Callingly tasks via Rube MCP and Composio.

Stars

★ 77,278

Source

GitHub

Updated

2026-10-17

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 77.3k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "callingly-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/callingly-automation/SKILL.md
2. Save it as ~/.claude/skills/callingly-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Automate Callingly operation workflows

When you need to turn Callingly operations into an automated workflow, first search tools, verify the connection, then execute the action. It fits workflows that must follow the current schema.

Execute safely against the latest schema

If tool parameters change often, this skill helps you fetch the latest tool definitions first and call them accordingly, reducing failures caused by mismatched fields.

Batch calls with session reuse

You can reuse a session within the same workflow and include the memory parameter for batch execution, which suits consecutive automation tasks.

// docs

AI summary

This document explains how to automate Callingly operations with Composio’s Callingly toolkit through Rube MCP. It covers prerequisites, how to connect Rube MCP, how to verify the Callingly connection, and the core workflow of discovering tools before execution. It also highlights session reuse, the memory parameter, pagination handling, and the need to avoid hardcoding schemas.

Show full docs ▾

Callingly Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/callingly

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["callingly"]
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 Callingly-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `callingly`
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

// FAQ

What does this skill do?

It automates Callingly tasks through Rube MCP and Composio's Callingly toolkit. The core flow is to search tools first, check the connection status, then execute against the latest schema.

What are the prerequisites?

You need Rube MCP connected and an active Callingly connection via RUBE_MANAGE_CONNECTIONS, with status ACTIVE. The docs also say no API keys are needed, only the Rube MCP endpoint.

Why must I search tools first?

Because tool schemas change. The docs explicitly require calling RUBE_SEARCH_TOOLS first to get current tool names, input schemas, and execution guidance before proceeding.

Automate Telnyx communication and number management tasks through Rube MCP.

ComposioGet→

$ loading_