What is ipdata-co-automation?

A workflow pattern to automate Ipdata co operations through Composio's Rube MCP toolkit.

Do I always need to search tools first?

Yes; tool schemas can change, so you must call RUBE_SEARCH_TOOLS before executing any tool.

What if the connection isn't ACTIVE?

Follow the returned auth link to complete setup, then recheck with RUBE_MANAGE_CONNECTIONS until status is ACTIVE.

ipdata-co-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/ipdata-co-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Ipdata co Automation via Rube MCP

Automate Ipdata co operations through Composio's Ipdata co toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ipdata_co

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Ipdata co connection via RUBE_MANAGE_CONNECTIONS with toolkit ipdata_co
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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit ipdata_co
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Ipdata co 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 Ipdata co task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ipdata_co"]
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 Ipdata co-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ipdata_co`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/ipdata-co-automation/SKILL.mdView on GitHub

Overview

Ipdata co automation uses Composio's Ipdata co toolkit through Rube MCP to run predefined Ipdata co workflows. It emphasizes discovering current tool schemas before execution to stay aligned with updates. This approach ensures reliable, schema-compliant automation of Ipdata co tasks.

How This Skill Works

Connect to Rube MCP and verify RUBE_SEARCH_TOOLS, then manage Ipdata co connections. Discover available tools, ensure the connection is ACTIVE, and execute the chosen tool with the proper arguments using RUBE_MULTI_EXECUTE_TOOL, including memory and session details for continuity.

When to Use It

When you need to automate Ipdata co tasks using Composio's Ipdata co toolkit
When you must always fetch current tool schemas before running any workflow
When you need to verify the Ipdata co connection is ACTIVE prior to execution
When performing bulk or repeated Ipdata co operations
When you want to reuse session IDs for workflow continuity

Quick Start

Step 1: RUBE_SEARCH_TOOLS for use_case: 'Ipdata co operations' to discover current tool schemas
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['ipdata_co'] and confirm ACTIVE status
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, proper arguments, memory: {} and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the discovered schema
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; create a new session for new workflows

Example Use Cases

Discover Ipdata co tools, select a fetch/enrichment tool, and execute it with RUBE_MULTI_EXECUTE_TOOL using the latest schema
Establish an ACTIVE ipdata_co connection and run a data enrichment task against a dataset
Perform bulk Ipdata co operations via RUBE_REMOTE_WORKBENCH with run_composio_tool for multiple tools
Handle pagination tokens when listing available Ipdata co tools and continue fetching until complete
Reuse a single session across steps in one automation flow to maintain state

Frequently Asked Questions

Add this skill to your agents