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

zoominfo-automation skill

/zoominfo-automation

This skill automates Zoominfo tasks via Rube MCP, discovering current tool schemas first to ensure accurate executions.

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

# Zoominfo Automation via Rube MCP

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

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

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Zoominfo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoominfo`
- 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 `zoominfo`
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: "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_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 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](https://composio.dev)*

Overview

This skill automates ZoomInfo operations using Composio's Zoominfo toolkit via the Rube MCP. It guides tool discovery, connection checks, and safe execution patterns so agents can run ZoomInfo searches, fetch records, and perform bulk tasks reliably. The skill emphasizes always discovering current tool schemas before use and managing session and memory parameters correctly.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available ZoomInfo tool slugs, input schemas, and recommended plans. It verifies or establishes an active ZoomInfo connection via RUBE_MANAGE_CONNECTIONS. Workflows run tools through RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH using schema-compliant arguments, session IDs, and a memory object. It handles pagination, connection status checks, and schema-driven execution to avoid runtime errors.

When to use it

  • Automate lead and company data lookups from ZoomInfo
  • Run bulk enrichment or export tasks through Composio toolchains
  • Integrate ZoomInfo calls inside multi-step agent workflows with stateful sessions
  • Perform repeatable searches while ensuring current tool schemas are used
  • Execute large or paginated queries reliably with session and memory management

Best practices

  • Always call RUBE_SEARCH_TOOLS first—tool schemas change frequently
  • Confirm ZoomInfo connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools
  • Use exact field names and types returned by the search response to build arguments
  • Include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session IDs for related workflow steps and create new ones for separate workflows
  • Check and follow pagination tokens until responses are complete

Example use cases

  • Discover available ZoomInfo search and export tools, then run a targeted company search and retrieve results
  • Verify or initiate the ZoomInfo connection, then enrich a batch of contacts using RUBE_REMOTE_WORKBENCH
  • Build an agent workflow that paginates through large result sets and writes normalized records to a CRM
  • Automate a recurring data quality job that checks schema changes, updates arguments, and re-runs enrichment tasks

FAQ

Do I need API keys to use Rube MCP with ZoomInfo?

No API keys are required to add the Rube MCP endpoint; you must however complete the ZoomInfo connection flow via RUBE_MANAGE_CONNECTIONS to activate access.

What happens if tool schemas change mid-workflow?

Always call RUBE_SEARCH_TOOLS at the start of a workflow and before critical steps; if schemas change, update arguments to match the returned schema and retry.