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

supadata-automation skill

safe

/supadata-automation

This skill automates Supadata tasks via Rube MCP, always discovering tool schemas first to ensure up-to-date integration and reliable workflows.

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

# Supadata Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["supadata"]
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 Supadata-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `supadata` |
| 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 Supadata operations using Composio's Supadata toolkit via the Rube MCP. It provides a reliable pattern for discovering tools, validating Supadata connections, and executing operations programmatically. The skill enforces runtime discovery of tool schemas so workflows stay resilient to API changes.

How this skill works

Before any action, the skill calls RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and execution recommendations. It verifies Supadata connectivity through RUBE_MANAGE_CONNECTIONS, then runs one or more toolkit methods via RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object) or RUBE_REMOTE_WORKBENCH for bulk tasks. The workflow reuses session IDs, handles pagination, and follows the discovered schema exactly.

When to use it

When you need to automate Supadata tasks (data ingestion, queries, or management) reliably from an agent.
When tool schemas may change and you want to avoid hardcoded arguments or slugs.
When running multi-step or bulk Supadata workflows that require session management and pagination.
When integrating Supadata operations into CI/CD or programmatic pipelines that must verify connections first.

Best practices

Always call RUBE_SEARCH_TOOLS at the start of a workflow to retrieve current tool schemas and recommended plans.
Confirm RUBE_MANAGE_CONNECTIONS reports an ACTIVE Supadata connection before executing any tool calls.
Pass an explicit memory object (even {}) to RUBE_MULTI_EXECUTE_TOOL and reuse the same session_id during a workflow.
Respect schema field names and types exactly; validate inputs against returned schemas before execution.
Handle pagination tokens in responses and continue fetching until no more pages remain.

Example use cases

Automate bulk data uploads: discover a bulk ingest tool, verify connection, and run RUBE_REMOTE_WORKBENCH with run_composio_tool().
Run scheduled Supadata queries: search for a query tool, supply schema-compliant args, and execute via RUBE_MULTI_EXECUTE_TOOL.
Onboard a new Supadata dataset: discover schema tools, create dataset resources, and confirm via connection checks.
Build a monitoring job that checks connection health and re-authenticates when RUBE_MANAGE_CONNECTIONS indicates non-ACTIVE status.

FAQ

Do I need API keys to connect to Rube MCP?

No API keys are required; add the Rube MCP endpoint (https://rube.app/mcp) to your client configuration and follow the connection flow.

What if a tool slug or input schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS at the start of each workflow and validate schemas before executing; generate a new session_id for new workflows to avoid inconsistent state.