What is Botpress automation via Rube MCP?

It is a workflow pattern to automate Botpress operations through Composio's Botpress toolkit using the Rube MCP bridge, ensuring current tool schemas are used.

Do I need API keys to use MCP?

No. You add the MCP endpoint (https://rube.app/mcp) as the MCP server; no API keys are required.

What should I do if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing; do not hardcode slugs or arguments, ensure memory is included, and verify the connection remains ACTIVE.

botpress-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Botpress Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/botpress

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Botpress operations through Composio's Botpress toolkit via Rube MCP. The workflow emphasizes always searching for current tool schemas and ensuring an ACTIVE Botpress connection before running any workflows.

How This Skill Works

Connect Rube MCP and the Botpress toolkit, then discover available tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Verify the Botpress connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, and finally execute tools using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and proper memory payload.

When to Use It

Automating a Botpress operation by discovering a specific tool slug and executing it with appropriate arguments
Validating Botpress connections and then running a Botpress workflow
Chaining multiple Botpress tasks in a single session using RUBE_MULTI_EXECUTE_TOOL
Handling pagination when discovering tools to ensure you fetch all available Botpress utilities
Reusing a session for recurring Botpress automations and avoiding hardcoded tool slugs

Quick Start

Step 1: Add Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client configuration
Step 2: Run RUBE_SEARCH_TOOLS with use_case: Botpress operations to discover available tools and schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkits: ["botpress"] and then RUBE_MULTI_EXECUTE_TOOL with a discovered slug

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools
Use exact field names and types from the search results; avoid hardcoding slugs or arguments
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for separate workflows

Example Use Cases

Discover a Botpress operation, connect to Botpress, and execute the tool with proper memory payload
Connect to a Botpress instance, verify ACTIVE, and run a sequence of tools in a single session
Fetch all Botpress tool schemas via RUBE_SEARCH_TOOLS and validate fields with RUBE_GET_TOOL_SCHEMAS
Use a persistent session for a recurring Botpress automation to maintain context across runs
Bulk Botpress tasks using RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH to run multiple tools in one go

Frequently Asked Questions

Add this skill to your agents