Brightpearl Automation
This skill automates Brightpearl operations using the Composio Brightpearl toolkit through Rube MCP. It's designed for users who want to streamline their Bri...
Install
npx promptshop add brightpearl-automationDetails
What This Skill Does
This skill automates Brightpearl operations using the Composio Brightpearl toolkit through Rube MCP. It's designed for users who want to streamline their Brightpearl e-commerce and retail management workflows. The skill requires an active Brightpearl connection and Rube MCP setup.
When to Use
Automate order processing. Manage inventory levels. Synchronize product data. Generate financial reports. Update customer information. Automate shipping confirmations.
Key Features
Manual Installation
- Manual installation
- View Full Skill Content
- The complete markdown content that gets installed
- 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
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", }] memory: {} session_id: "your_session_id"
Known Pitfalls
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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
- 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
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", }] memory: {} session_id: "your_session_id"
Known Pitfalls
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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 |