What is required to use this skill?

You need a connected Brightpearl via RUBE_MANAGE_CONNECTIONS and to discover tools first using RUBE_SEARCH_TOOLS defined by the Brightpearl toolkit.

How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing; it returns up-to-date tool slugs, input schemas, and execution plans.

How should data be passed to tools?

Pass schema-compliant arguments from the search results and include memory (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls.

brightpearl-automation

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

Files (1)

SKILL.md

2.9 KB

Brightpearl Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/brightpearl

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["brightpearl"]
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 Brightpearl-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `brightpearl`
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/brightpearl-automation/SKILL.md

View on GitHub

Overview

Automate Brightpearl operations through Composio's Brightpearl toolkit using Rube MCP. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and verifying an ACTIVE Brightpearl connection via RUBE_MANAGE_CONNECTIONS before execution.

How This Skill Works

Discover available Brightpearl tools with RUBE_SEARCH_TOOLS to view tool slugs and input schemas. Ensure the Brightpearl connection is ACTIVE using RUBE_MANAGE_CONNECTIONS. Execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and exact schema-compliant arguments, always including memory.

When to Use It

Starting a Brightpearl automation to perform an operation and needing current tool schemas via RUBE_SEARCH_TOOLS.
Verifying that the Brightpearl connection is ACTIVE before running any workflows with RUBE_MANAGE_CONNECTIONS.
Running a discovered tool slug with exact, schema-compliant arguments using RUBE_MULTI_EXECUTE_TOOL.
Reusing session IDs within a single workflow to maintain continuity and context.
Handling multi-page responses or large results by following pagination tokens in tool results.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case set to 'Brightpearl operations' to discover tools.
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['brightpearl'] to ensure ACTIVE connection.
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, exact arguments, and memory: {}

Best Practices

Always search first: Tool schemas change; never hardcode slugs or arguments without RUBE_SEARCH_TOOLS.
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE 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 management: Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Update a Brightpearl order status by executing the corresponding tool slug discovered via RUBE_SEARCH_TOOLS.
Sync Brightpearl inventory levels with an external supplier feed using a discovered tool.
Create a new Brightpearl customer record from CRM data with the appropriate tool.
Bulk update product pricing in Brightpearl using a discovered tool slug and exact args.
Generate a sales report by discovering the reporting tool and fetching results.

Frequently Asked Questions

Add this skill to your agents