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

unione-automation skill

/unione-automation

This skill automates Unione tasks via Rube MCP, always discovering current tool schemas before execution to ensure up-to-date workflows.

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

# Unione Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["unione"]
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 Unione-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `unione` |
| 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 Unione tasks through Composio's Unione toolkit using Rube MCP. It provides a reliable pattern for discovering current tool schemas, managing connections, and executing multi-tool workflows safely. The focus is on always searching tools first and validating connection status before running operations.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Unione tool slugs, input schemas, and recommended execution plans. It then verifies an active Unione connection via RUBE_MANAGE_CONNECTIONS and runs actions with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, including an explicit memory object and consistent session IDs. Tool schemas are never assumed; the workflow reads schemaRef or full tool schemas before building arguments.

When to use it

  • Automating Unione operations that require current tool schemas and safe execution.
  • Building multi-step workflows that call several Composio tools in sequence.
  • Running bulk or remote workbench jobs through Rube MCP for Unione.
  • Integrating Unione actions into CI/CD or scheduled automation where schema drift might occur.
  • Prototyping or debugging Unione tool usage with live schema discovery.

Best practices

  • Always call RUBE_SEARCH_TOOLS first to fetch current schemas and tool slugs.
  • Verify Unione is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing tools.
  • Include a memory object (even {}) in every RUBE_MULTI_EXECUTE_TOOL call.
  • Reuse session IDs for related steps; generate new session IDs for distinct workflows.
  • Respect exact field names and types returned by search; never hardcode arguments.
  • Handle pagination tokens on search responses and fetch until complete.

Example use cases

  • Discover available Unione connectors and run a data sync using RUBE_MULTI_EXECUTE_TOOL.
  • Set up and validate an Unione connection for a new account via RUBE_MANAGE_CONNECTIONS.
  • Execute a bulk transformation across many resources with RUBE_REMOTE_WORKBENCH and run_composio_tool().
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before generating automated input payloads.
  • Automate a multi-step workflow that chains several Unione tools with consistent session memory.

FAQ

What is the first call I should make?

Always call RUBE_SEARCH_TOOLS to retrieve current tool slugs and schemas for your Unione use case.

Do I need API keys to use Rube MCP?

No API keys are required when adding https://rube.app/mcp as an MCP server; just ensure RUBE_SEARCH_TOOLS responds.