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

accelo-automation skill

safe

/accelo-automation

This skill automates Accelo operations via Composio's MCP, enabling seamless task execution with real-time tool discovery and verified connections.

npx playbooks add skill composiohq/awesome-claude-skills --skill accelo-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.8 KB

---
name: accelo-automation
description: "Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Accelo Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/accelo](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `accelo`
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: "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](https://composio.dev)*

Overview

This skill automates Accelo operations through Composio’s Accelo toolkit using Rube MCP. It provides a safe, repeatable pattern for discovering tools, verifying connections, and executing Accelo tasks programmatically. Always query available tools first to adapt to live schemas and avoid hardcoded parameters.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover current tool slugs and input schemas for Accelo-related use cases. It verifies an active Accelo connection via RUBE_MANAGE_CONNECTIONS and executes tasks with RUBE_MULTI_EXECUTE_TOOL (including a memory object and session id). For bulk or complex flows it can call RUBE_REMOTE_WORKBENCH and fetch detailed schemas with RUBE_GET_TOOL_SCHEMAS.

When to use it

Automating ticket, person, company, or project updates in Accelo
Building scheduled or triggered workflows that act on Accelo data
Orchestrating multi-step Accelo operations where tool schemas may change
Performing bulk imports/edits with RUBE_REMOTE_WORKBENCH
Integrating Accelo actions into larger agent-driven automations

Best practices

Always call RUBE_SEARCH_TOOLS first — never hardcode tool slugs or argument shapes
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tool
Include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs across a workflow; generate new sessions for new workflows
Handle pagination tokens on responses to ensure complete data retrieval
Validate argument names and types exactly against the returned schemas

Example use cases

Create and assign a batch of tickets in Accelo after parsing incoming emails
Sync customer contact updates from an external CRM into Accelo using discovered schemas
Run a scheduled job that closes stale tasks and logs results to memory
Execute a multi-step pipeline: create company, add contacts, attach initial project
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before implementing a complex integration

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration.

What if a tool schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS for the current workflow or generate a new session to pick up schema changes before executing tools.

Is connection setup necessary every time?

Verify the Accelo connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running workflows; you only need to authenticate if status is not ACTIVE.