Do I need an API key?

No API keys are needed. Add https://rube.app/mcp as your MCP server to enable Rube MCP access.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas before executing any workflow.

How do I ensure the Accelo connection is ready?

Call RUBE_MANAGE_CONNECTIONS with the accelo toolkit and confirm the status is ACTIVE before running workflows.

accelo-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Accelo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/accelo

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Accelo operations using Composio's Accelo toolkit through Rube MCP. The skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and ensuring an active Accelo connection via RUBE_MANAGE_CONNECTIONS. Typical workflows follow tool discovery, connection verification, then tool execution with RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

Connect Rube MCP and ensure the Accelo toolkit is ready. First, call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas, then verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and the active session_id.

When to Use It

Automating a recurring Accelo task (e.g., project creation or ticketing) after tools are discovered.
When tool schemas change and you must fetch the latest slugs via RUBE_SEARCH_TOOLS before running workflows.
Before any Accelo workflow, verify an ACTIVE Accelo connection with RUBE_MANAGE_CONNECTIONS.
Executing a single or batch Accelo actions using RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs.
Reusing a session ID across steps of a workflow to maintain context and continuity.

Quick Start

Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Accelo operations", known_fields: ""}] session: {generate_id: true}
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["accelo"] session_id: "your_session_id"
Step 3: RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* schema-compliant args from search results */}}] memory: {} session_id: "your_session_id"

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the tool schemas returned by search results.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for new workflows.

Example Use Cases

Create a new Accelo project by selecting the appropriate tool slug from RUBE_SEARCH_TOOLS and supplying required fields.
Log a time entry in Accelo by using the time_entry tool slug retrieved from search results with correct arguments.
Update a client contact in Accelo using the contact_update tool slug and schema-compliant fields.
Bulk close or update multiple Accelo items by executing several tools in sequence via RUBE_MULTI_EXECUTE_TOOL.
Resume a paused workflow by reusing an existing session_id and continuing with subsequent tool executions.

Frequently Asked Questions

Add this skill to your agents