What is bolna-automation?

It is a workflow to automate Bolna tasks using Composio's Bolna toolkit through the Rube MCP interface.

Do I need API keys to use it?

No API keys are required. Add the MCP endpoint (e.g., https://rube.app/mcp), ensure RUBE_SEARCH_TOOLS works, and establish an active Bolna connection.

How do I handle changing tool schemas?

Always run RUBE_SEARCH_TOOLS to fetch current schemas before executing tools and avoid hardcoding tool slugs or argument structures.

bolna-automation

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

Files (1)

SKILL.md

2.8 KB

Bolna Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bolna

Prerequisites

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

Step 2: Check Connection

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

Overview

Bolna Automation via Rube MCP enables automated Bolna operations through Composio's Bolna toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an active Bolna connection via RUBE_MANAGE_CONNECTIONS, and executing tools with RUBE_MULTI_EXECUTE_TOOL. This approach reduces manual setup and keeps tools aligned with the latest schemas.

How This Skill Works

First, use RUBE_SEARCH_TOOLS to fetch available Bolna tool slugs and their input schemas. Next, verify and activate the Bolna connection using RUBE_MANAGE_CONNECTIONS, then run a selected tool with RUBE_MULTI_EXECUTE_TOOL, passing the discovered arguments and a memory payload. RUBE_MULTI_EXECUTE_TOOL requires a session_id and includes memory={}, ensuring stateful execution.

When to Use It

When starting a new Bolna task automation and you need the latest tool schemas before proceeding
When embedding Bolna workflows into a larger Rube MCP automation pipeline
When preparing and validating the Bolna connection before running tools to ensure ACTIVE status
When running multiple Bolna tools in a single session to reduce setup overhead
When adapting to changing tool schemas and avoiding hardcoded slugs or arguments

Quick Start

Step 1: Connect to Rube MCP and verify RUBE_SEARCH_TOOLS responds for Bolna
Step 2: Discover available Bolna tools with RUBE_SEARCH_TOOLS using use_case: 'Bolna operations' and start a session
Step 3: Check connection status with RUBE_MANAGE_CONNECTIONS, then execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and memory {}

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current Bolna tool schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results; do not hardcode
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Automate a Bolna data reconciliation task by discovering tools, establishing a Bolna connection, and executing the appropriate tool with dynamic inputs
Batch-process multiple Bolna operations in one session to reduce repeated setup steps
Update an automation to reflect newly introduced tool schemas without hardcoding slugs
Validate tool schemas by performing discovery and then executing a tool with dynamic, schema-driven arguments
Handle pagination in tool discovery to fetch all available Bolna tools and their schemas

Frequently Asked Questions

Add this skill to your agents