Do I need API keys to use this skill?

No API keys are required. You connect via the Rube MCP endpoint and manage the Dropcontact toolkit through the provided actions.

Why should I always call RUBE_SEARCH_TOOLS before running a workflow?

Tool schemas change over time. RUBE_SEARCH_TOOLS returns current tool slugs and required arguments, preventing hardcoded, outdated calls.

How do I ensure the workflow uses an ACTIVE connection?

Use RUBE_MANAGE_CONNECTIONS to check the toolkit connection status and wait for ACTIVE before executing any tools; re-authenticate if needed.

dropcontact-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Dropcontact Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/dropcontact

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dropcontact"]
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 Dropcontact-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dropcontact`
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/dropcontact-automation/SKILL.md

View on GitHub

Overview

Automates Dropcontact operations through Composio's Rube MCP toolkit. It orchestrates tool discovery, connection management, and execution by calling discovered tool slugs with exact schemas. Always fetch current tool schemas before running workflows to avoid breakages.

How This Skill Works

The workflow starts by verifying RUBE_SEARCH_TOOLS is available, then uses RUBE_MANAGE_CONNECTIONS to ensure an active 'dropcontact' connection. Tools are executed with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and a memory payload, tied to a session_id for continuity.

When to Use It

Enrich a single contact's email or company data using a Dropcontact tool
Batch-enrich hundreds of leads by discovering tool schemas and executing multiple tools
Set up or re-verify the Dropcontact connection before running workflows
Debug a workflow by fetching current tool schemas with RUBE_SEARCH_TOOLS first
Maintain state across steps by reusing session IDs and memory in a sequence

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS
Step 2: Manage the Dropcontact connection with RUBE_MANAGE_CONNECTIONS; complete auth if needed and confirm ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using a session_id and memory

Best Practices

Always search for current tools first; tool schemas can change
Check that the Dropcontact connection is ACTIVE before execution
Use exact field names and types from search results to avoid schema errors
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs across related workflows to maintain state

Example Use Cases

Enrich 50 leads by discovering the correct Dropcontact tool slug via RUBE_SEARCH_TOOLS and executing with a memory payload containing the leads list
Run a sequence of enrichment steps for a marketing campaign using the same session_id and memory across multiple tool executions
Reestablish an inactive Dropcontact connection by calling RUBE_MANAGE_CONNECTIONS and following the auth flow until ACTIVE
Debug a workflow by first calling RUBE_SEARCH_TOOLS to fetch up-to-date tool schemas before execution
Perform bulk operations with RUBE_MULTI_EXECUTE_TOOL and review full tool schemas with RUBE_GET_TOOL_SCHEMAS

Frequently Asked Questions

Add this skill to your agents