What is required to start?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must respond, and an ACTIVE Landbot connection is required.

Why should I always search for tools before executing?

Tool schemas change over time; searching provides current slugs and input schemas to prevent failed executions.

How do I handle tool schema changes?

Re-run RUBE_SEARCH_TOOLS to refresh slugs and input schemas, then re-run the workflow with updated arguments and memory.

landbot-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Landbot Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/landbot

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Landbot tasks using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, maintaining an ACTIVE Landbot connection, and executing discovered tools via RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

Workflow: discover available Landbot tools with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas. Then verify the Landbot connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing memory and a session_id.

When to Use It

You need to perform a Landbot operation where tool schemas may change and you must rely on current slugs from RUBE_SEARCH_TOOLS.
Setting up a new Landbot integration requires discovering available tools before configuring workflows.
Executing batch Landbot tasks across multiple bots within a single session, reusing session IDs where appropriate.
Troubleshooting failures by re-running discovery to refresh tool slugs and input schemas after a tool update.
Regularly validating the connection and schemas before running mission-critical Landbot workflows.

Quick Start

Step 1: Verify Rube MCP is available by ensuring RUBE_SEARCH_TOOLS responds.
Step 2: Manage Landbot connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to retrieve current tool slugs and input schemas.
Check the Landbot connection with RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE before execution.
Use exact field names and types from the tool search results to avoid schema mismatches.
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 sending a message in Landbot using a discovered tool slug from RUBE_SEARCH_TOOLS.
Update contact fields in Landbot based on a lead status from an integrated CRM using a current tool input schema.
Bulk update bot configurations across multiple Landbot bots within a single RUBE_MULTI_EXECUTE_TOOL session.
Validate and adapt to new Landbot tool schemas after a Composio update by re-discovering tools.
Troubleshoot a failing Landbot task by refreshing tool schemas and re-running the workflow with updated args.

Frequently Asked Questions

Add this skill to your agents