callingly-automation

Callingly Automation - Call Back Task Automation Skill

Skill Overview

Automate Callingly call-back tasks with Rube MCP without needing an API key. Supports tool discovery, connection management, and batch execution.

Use Cases

1. Sales Team Call-Back Automation

When a sales team needs to process leads’ phone calls in bulk, use this skill to automatically schedule Callingly call-back tasks without manually operating each one. After discovering available tools with RUBE_SEARCH_TOOLS, use RUBE_MULTI_EXECUTE_TOOL to batch import contacts and automatically assign call-back tasks.

2. CRM and Phone System Integration

To sync customer data from a CRM system to Callingly, use Rube MCP’s RUBE_REMOTE_WORKBENCH to run the run_composio_tool() function, enabling bidirectional data sync and ensuring customer information is updated in real time.

3. Workflow Orchestration and Automation

In complex business workflows, Callingly Automation can serve as one step within a larger workflow and work alongside other MCP tools. For example: automatically add new leads to the CRM → trigger Callingly call-backs → write the results back to the database.

Core Features

1. Dynamic Tool Discovery

Use RUBE_SEARCH_TOOLS to fetch the latest Callingly tool schema in real time, ensuring compatibility with the current API version. This is the first step when using the skill: it returns the available tool slugs, input parameters, and a recommended execution plan.

2. No-Key Connection Management

Just add the https://rube.app/mcp endpoint to your MCP client to get started—no API key required. Use RUBE_MANAGE_CONNECTIONS to check and manage the Callingly connection status, ensuring the connection is activated before workflow execution.

3. Batch Task Execution

Use RUBE_MULTI_EXECUTE_TOOL to perform multiple Callingly operations within a single session, reusing the session ID to improve efficiency. Supports combinations of operations such as importing contacts, scheduling call-backs, querying statuses, and more.

FAQ

Does Callingly Automation require an API key?

No. This skill accesses Callingly through the proxy layer provided by Rube MCP (Composio). Add the https://rube.app/mcp endpoint to your MCP client, then authorize your Callingly account using RUBE_MANAGE_CONNECTIONS.

How can I confirm whether the Callingly connection was successful?

Call RUBE_MANAGE_CONNECTIONS and specify the toolkit as callingly to check the returned connection status. If the status is ACTIVE, the connection succeeded. If not, complete account binding using the authorization link returned.

What should I do if tool execution fails?

First, confirm you called RUBE_SEARCH_TOOLS to fetch the latest tool schema (hard-coded slugs may become invalid after API updates). Next, check whether the arguments field of RUBE_MULTI_EXECUTE_TOOL exactly matches the schema from the search results—field names and types must be identical. Finally, ensure the session ID is correctly passed and includes the memory parameter.