zoominfo-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/zoominfo-automation --openclawZoominfo Automation via Rube MCP
Automate Zoominfo operations through Composio's Zoominfo toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/zoominfo
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Zoominfo connection via
RUBE_MANAGE_CONNECTIONSwith toolkitzoominfo - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitzoominfo - 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: "Zoominfo 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 Zoominfo task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["zoominfo"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Zoominfo-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit zoominfo |
| 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/zoominfo-automation/SKILL.mdView on GitHub Overview
This skill enables automated Zoominfo operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing any workflow to keep integrations up to date.
How This Skill Works
Workflows start by discovering available Zoominfo tools with RUBE_SEARCH_TOOLS, then verify or establish the Zoominfo connection via RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool through RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and the required arguments, always including a memory object and a session_id sourced from the current workflow.
When to Use It
- When you need repeatable Zoominfo tasks without manual clicks
- When tool schemas or available operations change and you must fetch latest slugs first
- When integrating Zoominfo actions into larger automated workflows
- When validating and reusing a session across multiple Zoominfo steps
- When handling large results with pagination tokens and sequential calls
Quick Start
- Step 1: Add the Rube MCP endpoint https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS
- Step 2: Discover Zoominfo tools with RUBE_SEARCH_TOOLS use_case Zoominfo operations and note the tool slugs
- Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using a discovered slug, a memory object, and a session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool slugs and schemas
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the discovered schema
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
- Reuse session IDs within a workflow and avoid hardcoding slugs
Example Use Cases
- Auto enrich a lead by discovering an enrich_contact tool and running it with the lead email
- Sync CRM contacts by connecting Zoominfo and executing update_contact across sessions
- Batch fetch company data using a bulk_get_companies tool and handle pagination tokens
- Validate tool schemas before each run to prevent mismatches
- Use a multi step workflow to enrich accounts and export results to a CRM