home / skills / composiohq / awesome-claude-skills / baserow-automation

baserow-automation skill

safe

/baserow-automation

This skill automates Baserow tasks using Rube MCP, ensuring tools are discovered first and connections verified for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill baserow-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: baserow-automation
description: "Automate Baserow tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Baserow Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/baserow](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `baserow`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Baserow tasks using Composio's Baserow toolkit via Rube MCP. It provides a clear workflow: discover tools, verify connections, then execute toolkit actions programmatically. It emphasizes always searching tools first to get current schemas and avoiding hardcoded tool definitions.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Baserow tool slugs and input schemas, then RUBE_MANAGE_CONNECTIONS to confirm an active Baserow connection. After discovery and connection checks, it runs actions with RUBE_MULTI_EXECUTE_TOOL (including a memory object) or bulk operations through RUBE_REMOTE_WORKBENCH. Responses must be paginated when necessary and session IDs reused within a workflow.

When to use it

Automating CRUD operations in Baserow from an agent flow
Running bulk updates or imports that require toolkit discovery first
Integrating Baserow actions into larger Rube MCP workflow sequences
Creating repeatable, session-based automation with schema validation
Fetching full tool schemas before building dynamic UI or clients

Best practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and exact input schemas
Verify Baserow connection via RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE
Never hardcode tool slugs or argument names; use the returned schema fields and types
Include a memory object (can be empty {}) in all RUBE_MULTI_EXECUTE_TOOL calls
Reuse a session_id across related calls; generate a new session for separate workflows
Handle pagination tokens in responses and iterate until all data is retrieved

Example use cases

Discover table-specific create and update tools, then insert rows using schema-compliant arguments
Run a bulk migration by calling RUBE_REMOTE_WORKBENCH with run_composio_tool() for many records
Automate connection setup checks and prompt for auth when RUBE_MANAGE_CONNECTIONS reports inactive
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a dynamic form in an app
Build session-based workflows that search, validate, and execute a sequence of Baserow operations

FAQ

Do I need API keys to use Rube MCP with this skill?

No API keys are required for Rube MCP; add https://rube.app/mcp as an MCP server in your client configuration.

What if a tool schema changed since I last used it?

Call RUBE_SEARCH_TOOLS again to get the updated schema; never rely on cached or hardcoded names and types.