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

acculynx-automation skill

safe

/acculynx-automation

This skill automates Acculynx tasks via Rube MCP, ensuring tool schemas are current by always searching tools first.

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

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

Files (1)

SKILL.md

2.9 KB

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

# Acculynx Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/acculynx](https://composio.dev/toolkits/acculynx)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["acculynx"]
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 Acculynx-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `acculynx` |
| 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 Acculynx tasks using Composio's Acculynx toolkit via the Rube MCP. It provides a clear workflow for discovering tools, validating connections, and executing operations programmatically. The emphasis is on always searching tools first to get current schemas and avoiding hardcoded inputs.

How this skill works

The skill uses Rube MCP endpoints to discover available Acculynx tools, verify an active Acculynx connection, and run one or more toolkit actions. Typical calls include RUBE_SEARCH_TOOLS to fetch tool slugs and schemas, RUBE_MANAGE_CONNECTIONS to check or complete connection setup, and RUBE_MULTI_EXECUTE_TOOL to perform operations with schema-compliant arguments. It expects session reuse, explicit memory parameters, and handling of pagination tokens in responses.

When to use it

Automating routine Acculynx operations like creating jobs, updating schedules, or fetching reports.
Building agents or workflows that must call Acculynx through Composio toolkits reliably.
Integrating Acculynx actions into broader orchestration pipelines that require session and state management.
Performing bulk or batched operations that benefit from Rube MCP multi-execution or remote workbench.

Best practices

Always call RUBE_SEARCH_TOOLS before using any tool to obtain the latest tool slugs and input schemas.
Verify the Acculynx connection with RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE before execution.
Supply a memory object (can be empty) on RUBE_MULTI_EXECUTE_TOOL calls and reuse session IDs within a workflow.
Match field names and types exactly as returned by the tool search; do not hardcode argument shapes.
Handle pagination tokens and follow fetch-until-complete patterns for list responses.

Example use cases

Discover available Acculynx job-management tools and programmatically create new job entries with validated inputs.
Check connection status, open the provided auth link if needed, then run a workflow to export recent estimates.
Run batched updates to schedules using RUBE_MULTI_EXECUTE_TOOL and maintain session-based state across calls.
Use RUBE_GET_TOOL_SCHEMAS to inspect full schemas for a complex tool before building input validation logic.
Execute bulk operations through RUBE_REMOTE_WORKBENCH with run_composio_tool() for high-volume workflows.

FAQ

Do I need API keys to add 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?

Always re-run RUBE_SEARCH_TOOLS to get the current schema and update your arguments to match exactly.