Do I always need to search tools first?

Yes, to obtain the latest tool schemas and avoid hardcoding.

How do I ensure the Baserow connection is ready?

Check the RUBE_MANAGE_CONNECTIONS status and wait for ACTIVE before executing tools.

What tool supports bulk operations?

RUBE_REMOTE_WORKBENCH with run_composio_tool() enables bulk or remote execution; use it when you need to run many tasks in one workflow.

baserow-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Baserow Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/baserow

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Baserow operations through Composio's Baserow toolkit via Rube MCP. This skill emphasizes discovering current tool schemas before execution and requires a live ACTIVE Baserow connection. Follow the core workflow to perform reliable, schema-compliant tasks and bulk operations.

How This Skill Works

You first discover available tools with RUBE_SEARCH_TOOLS, then verify or establish a Baserow connection with RUBE_MANAGE_CONNECTIONS, and finally execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with the correct arguments and session context. Tool slugs and arguments come from the live schemas, ensuring compatibility as schemas evolve.

When to Use It

When you need to automate a Baserow task but must start by discovering the current tool schemas with RUBE_SEARCH_TOOLS.
When establishing or validating a Baserow connection before running workflows using the baserow toolkit.
When you have a discovered tool slug and need to execute it with exact, schema-compliant arguments.
When performing bulk or batch Baserow operations using RUBE_REMOTE_WORKBENCH and run_composio_tool().
When building multi-step automations that reuse a session ID for continued workflow context.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit baserow and confirm the connection shows ACTIVE.
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and correct arguments, including memory.

Best Practices

Always call RUBE_SEARCH_TOOLS to fetch up-to-date tool schemas.
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before tool execution.
Use exact field names and types from search results; do not hardcode.
Include the memory parameter in all 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

An automation creates a new Baserow record when a form submission arrives, using a discovered tool slug and a memory context.
A workflow updates a Baserow row by retrieving the correct tool slug from RUBE_SEARCH_TOOLS and executing with precise arguments.
A bulk-create scenario across multiple Baserow tables using RUBE_REMOTE_WORKBENCH and run_composio_tool().
A startup routine that connects to Baserow and validates ACTIVE status before downstream tasks run.
A maintenance task that fetches current schemas, then plans a multi-step automation around those tools.

Frequently Asked Questions

Add this skill to your agents