Telnyx Automation

What This Skill Does

The Telnyx Automation skill allows users to automate Telnyx operations through Composio's Telnyx toolkit via Rube MCP. It is designed for developers and system administrators who need to manage Telnyx services programmatically. The skill requires an active Telnyx connection and Rube MCP setup.

When to Use

Provisioning phone numbers Configuring call routing Managing SMS services Automating account settings Monitoring Telnyx resources Integrating Telnyx with other systems

Key Features

Automates Telnyx tasks via Rube MCPUses Composio's Telnyx toolkit Discovers available tools dynamically Checks connection status before execution Enforces schema compliance for arguments Provides example workflows for common tasks 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