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

apex27-automation skill

safe

/apex27-automation

This skill automates Apex27 workflows via Rube MCP, ensuring real-time tool discovery, validated connections, and schema-compliant executions for reliable

npx playbooks add skill composiohq/awesome-claude-skills --skill apex27-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: apex27-automation
description: "Automate Apex27 tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Apex27 Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["apex27"]
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 Apex27-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apex27` |
| 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 Apex27 tasks through Composio's Apex27 toolkit using Rube MCP. It provides a repeatable pattern for discovering tools, validating connections, and executing toolkit operations safely. Follow the search-first approach to avoid schema drift and ensure reliable workflows.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended plans. It validates or establishes an Apex27 connection with RUBE_MANAGE_CONNECTIONS, then runs actions with RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object) or RUBE_REMOTE_WORKBENCH for bulk operations. Always inspect search results and schemaRefs before forming arguments.

When to use it

Automating Apex27 API tasks or admin workflows programmatically
Running multi-step Apex27 operations that require current tool schemas
Orchestrating bulk or scheduled operations via Composio toolkits
Building agent-driven integrations that must respect live tool contracts
Migrating or repeating workflows where session reuse and pagination matter

Best practices

Always call RUBE_SEARCH_TOOLS first to retrieve current schemas and tool slugs
Verify connection status via RUBE_MANAGE_CONNECTIONS; complete auth if not ACTIVE
Pass the memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs inside a workflow and create new sessions for separate runs
Respect exact field names and types from search results to avoid schema errors
Handle pagination tokens and iterate until responses are complete

Example use cases

Discover available Apex27 operations and run a configuration change in one flow
Authorize an Apex27 connection interactively, then execute a secure data export
Run bulk transformations using RUBE_REMOTE_WORKBENCH with run_composio_tool()
Automate a multi-step deployment by chaining discovered tools with RUBE_MULTI_EXECUTE_TOOL
Implement scheduled agent workflows that check schemas before each run

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server; no API keys are required for the MCP endpoint.

What if a tool slug or schema changed?

Run RUBE_SEARCH_TOOLS before executing any operation to get the updated slug and schema. Never hardcode values.