Deepgram Automation

What This Skill Does

When to Use

• Transcribe audio files
• Analyze audio content
• Extract insights from speech
• Automate audio processing
• Integrate with voice applications
• Monitor audio streams

Key Features

Manual Installation

• Manual installation
• View Full Skill Content
• The complete markdown content that gets installed
• Deepgram Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/deepgram

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Deepgram connection via RUBE_MANAGE_CONNECTIONS with toolkit deepgram Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit deepgram 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: "Deepgram 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 Deepgram task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["deepgram"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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

• Powered by Composio
• Deepgram Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/deepgram

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Deepgram connection via RUBE_MANAGE_CONNECTIONS with toolkit deepgram Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit deepgram 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: "Deepgram 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 Deepgram task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["deepgram"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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