What is telnyx-automation?

A Composio-based skill to automate Telnyx tasks via Rube MCP, using live tool schemas fetched with RUBE_SEARCH_TOOLS.

Do I need to connect Telnyx and Rube MCP first?

Yes. You must have an ACTIVE Telnyx connection configured via RUBE_MANAGE_CONNECTIONS with the telnyx toolkit and ensure RUBE_SEARCH_TOOLS is available.

What are common pitfalls I should avoid?

Always search for current tool schemas before execution, verify ACTIVE connection, use exact field names/types from search results, include memory in calls, and reuse session IDs where appropriate while handling pagination.

telnyx-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Telnyx Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/telnyx

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Telnyx operations through Composio's Telnyx toolkit using Rube MCP. Requires an active Telnyx connection and a connected Rube MCP, with a mandatory initial tool-schema discovery via RUBE_SEARCH_TOOLS to avoid hardcoding slugs.

How This Skill Works

The skill discovers current tool schemas with RUBE_SEARCH_TOOLS, then establishes and verifies an ACTIVE Telnyx connection via RUBE_MANAGE_CONNECTIONS. Once ready, it executes discovered tools using RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id. Always perform tool discovery first to ensure you’re using up-to-date slugs and schemas.

When to Use It

After connecting to Rube MCP, to perform a Telnyx operation without hardcoding tool slugs.
When tool schemas change and you need the latest input fields before execution.
To verify an ACTIVE Telnyx connection before running any workflows.
For bulk or multi-step Telnyx tasks using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH.
When reusing session IDs within a workflow and managing pagination in tool responses.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'telnyx' and ensure the connection status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover available Telnyx tools, then run a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the discovered tool schemas.
Include the memory parameter (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs within a workflow and handle pagination when responses are paginated.

Example Use Cases

Discover a Telnyx tool slug with RUBE_SEARCH_TOOLS and then run an SMS send task via RUBE_MULTI_EXECUTE_TOOL.
Connect to Telnyx using RUBE_MANAGE_CONNECTIONS with toolkit 'telnyx' and confirm ACTIVE before workflows.
Execute a discovered Telnyx tool slug with the correct arguments and a session_id.
Perform bulk Telnyx updates using RUBE_REMOTE_WORKBENCH and run_composio_tool for multiple resources.
Fetch full tool schemas using RUBE_GET_TOOL_SCHEMAS to validate fields before automation.

Frequently Asked Questions

Add this skill to your agents