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

boloforms-automation skill

safe

/boloforms-automation

This skill helps you automate Boloforms operations via Rube MCP by discovering current tool schemas and executing compliant tools.

npx playbooks add skill composiohq/awesome-claude-skills --skill boloforms-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: boloforms-automation
description: "Automate Boloforms tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Boloforms Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/boloforms](https://composio.dev/toolkits/boloforms)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["boloforms"]
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 Boloforms-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `boloforms` |
| 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 Boloforms tasks using Composio's Boloforms toolkit via the Rube MCP. It provides a concise pattern for discovering tools, verifying connections, and executing toolkit operations reliably. The skill enforces searching tool schemas first to avoid breaking changes and ensures session and memory handling are correct.

How this skill works

First it calls RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. Next it validates the Boloforms connection with RUBE_MANAGE_CONNECTIONS and only proceeds if the connection is ACTIVE. Finally it runs one or more toolkit operations via RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, passing schema-compliant arguments, a session_id, and a memory object.

When to use it

Automating form creation, updates, or bulk operations in Boloforms from an agent workflow
Integrating Boloforms actions into a larger Composio orchestration or pipeline
Building reproducible automation that must adapt to changing tool schemas
Running multi-step workflows where session state and pagination must be preserved

Best practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas before executing anything
Verify toolkit connection with RUBE_MANAGE_CONNECTIONS and complete any returned auth flow until status is ACTIVE
Pass an explicit memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session_id within the workflow
Follow exact field names and types from the search results; do not hardcode arguments or assume schema stability
Watch for pagination tokens in responses and continue fetching until results are complete

Example use cases

Create a new Boloforms form by discovering the create_form tool, filling schema fields, and executing via RUBE_MULTI_EXECUTE_TOOL
Bulk-update form settings across many forms using RUBE_REMOTE_WORKBENCH with run_composio_tool() to parallelize operations
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to build a dynamic UI or validation layer before execution
Orchestrate a multi-step workflow that searches tools, confirms connection, executes tools, and stores outputs in memory for follow-up

FAQ

Do I need an API key to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration—no API key is required; just the endpoint.

What if the toolkit connection isn't ACTIVE?

Call RUBE_MANAGE_CONNECTIONS and follow the returned auth link to complete setup. Confirm ACTIVE status before running workflows.