Happy Scribe Automation

What This Skill Does

The Happy Scribe Automation skill allows users to automate interactions with the Happy Scribe transcription service. It leverages the Composio Happy Scribe toolkit via Rube MCP. This skill is designed for users who need to programmatically manage transcriptions, translations, and other tasks within Happy Scribe.

When to Use

• Automate transcription requests.
• Download completed transcriptions.
• Translate transcriptions to other languages.
• Manage Happy Scribe files.
• Integrate with audio/video workflows.
• Monitor transcription status.

Key Features

• Requires Rube MCP and active Happy Scribe connection.
• Uses RUBE_SEARCH_TOOLS for tool discovery.
• Employs RUBE_MANAGE_CONNECTIONS for connection management.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.Tool schemas are dynamically retrieved.
• Connection status is checked before execution.

Automate Happy Scribe operations through Composio's Happy Scribe toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/happy_scribe

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["happy_scribe"] 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

Automate Happy Scribe operations through Composio's Happy Scribe toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/happy_scribe

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["happy_scribe"] 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