Do I need API keys to use Byteforms automation?

No — you add the MCP endpoint (for example, https://rube.app/mcp) and proceed; API keys are not required.

Why should I always search tools first?

Tool slugs and input schemas can change, so you must fetch current schemas with RUBE_SEARCH_TOOLS instead of hardcoding.

How do I ensure the Byteforms connection is ready?

Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE; if not, follow the provided auth link to complete setup.

byteforms-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Byteforms Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/byteforms

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Byteforms operations through Composio's Byteforms toolkit via Rube MCP. It guides you to discover current tool schemas, establish an ACTIVE Byteforms connection, and execute schema-driven tasks without hardcoding slugs.

How This Skill Works

First, fetch up-to-date Byteforms tool slugs and input schemas with RUBE_SEARCH_TOOLS. Then verify or establish a Byteforms connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, run tools using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and schema-compliant arguments, always including memory.

When to Use It

When you need to automate Byteforms tasks and want current tool schemas
When starting a Byteforms workflow, begin with tool discovery to avoid hardcoding slugs
When preparing to run a tool, verify an ACTIVE Rube MCP connection for Byteforms
When executing multiple Byteforms steps in a session, reuse the same session_id across steps
When tool schemas or arguments can change, fetch fresh schemas before execution

Quick Start

Step 1: Discover tools with RUBE_SEARCH_TOOLS to obtain Byteforms tool slugs
Step 2: Connect your Byteforms toolkit via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, schema args, and memory

Best Practices

Always call RUBE_SEARCH_TOOLS before any run to fetch current tool schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results instead of guessing
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if {})
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Automate a Byteforms invoice processing task by discovering the relevant tool slug, connecting, and executing with the provided input fields
Batch validate Byteforms data by reusing a session and executing multiple tools in sequence
Sync Byteforms outputs to an external CRM by running a tool with the schema-derived arguments and memory
Generate Byteforms reports by discovering the reporting tool, confirming ACTIVE connection, and executing with the report parameters
Handle pagination by using RUBE_SEARCH_TOOLS repeatedly and continuing until all pages are retrieved

Frequently Asked Questions

Add this skill to your agents