retellai-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/retellai-automation --openclawRetellai Automation via Rube MCP
Automate Retellai operations through Composio's Retellai toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/retellai
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Retellai connection via
RUBE_MANAGE_CONNECTIONSwith toolkitretellai - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitretellai - 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: "Retellai 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 Retellai task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["retellai"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Retellai-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit retellai |
| 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/retellai-automation/SKILL.mdView on GitHub Overview
Automate Retellai operations using Composio's Retellai toolkit through Rube MCP. This workflow emphasizes discovering current tool schemas first with RUBE_SEARCH_TOOLS and ensuring an active connection before execution.
How This Skill Works
The skill follows a core workflow: discover available Retellai tools with RUBE_SEARCH_TOOLS, verify connectivity with RUBE_MANAGE_CONNECTIONS, and execute the selected tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments. Always include a memory object and a valid session_id, and refresh tool schemas if changes occur.
When to Use It
- You need to run a Retellai operation by first discovering current tool options and schemas.
- You must confirm an active Retellai connection before workflow execution.
- You are executing a single tool using discovered slug and required arguments.
- You want to perform bulk or chained Retellai actions in one session.
- Tool schemas may have changed; re-discover tools to refresh slugs and fields.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS with use_case set to Retellai operations.
- Step 2: RUBE_MANAGE_CONNECTIONS for toolkit retellai and confirm ACTIVE.
- Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug and discovered arguments; include memory and session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any Retellai tool.
- Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running workflows.
- Use exact field names and types from the current tool schemas.
- Include a memory payload in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and avoid hardcoding tool slugs.
Example Use Cases
- Discover Retellai tools and execute a selected one with the discovered slug.
- Establish a Retellai connection via RUBE_MANAGE_CONNECTIONS and run a tool in an ACTIVE session.
- Execute multiple Retellai tools in a single session using RUBE_MULTI_EXECUTE_TOOL.
- Use RUBE_GET_TOOL_SCHEMAS to inspect complete schemas before integration.
- Re-discover tools when schemas change to fetch updated slugs and fields.