zerobounce-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/zerobounce-automation --openclawZerobounce Automation via Rube MCP
Automate Zerobounce operations through Composio's Zerobounce toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/zerobounce
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Zerobounce connection via
RUBE_MANAGE_CONNECTIONSwith toolkitzerobounce - 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 toolkitzerobounce - 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: "Zerobounce 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 Zerobounce task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["zerobounce"]
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 Zerobounce-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit zerobounce |
| 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/zerobounce-automation/SKILL.mdView on GitHub Overview
Automates Zerobounce operations by leveraging Composio's Zerobounce toolkit through Rube MCP. It requires discovering current tool schemas with RUBE_SEARCH_TOOLS before every workflow and maintaining an ACTIVE Zerobounce connection. This approach reduces fragility from schema changes and enables repeatable, scalable automation.
How This Skill Works
Connect Rube MCP as an MCP server and verify RUBE_SEARCH_TOOLS responds. Use RUBE_MANAGE_CONNECTIONS with toolkits: ['zerobounce'] to establish an ACTIVE Zerobounce connection, then discover tools with RUBE_SEARCH_TOOLS and pick a tool_slug. Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} as required, reusing the session ID across steps.
When to Use It
- Regularly verify or clean email lists using Zerobounce during onboarding flows.
- Perform bulk bounce checks on marketing lists via discovered Zerobounce tools.
- Automate sequential Zerobounce actions in a single session (discover, connect, execute) to reduce manual steps.
- Handle tool schema changes safely by always re-reading tool schemas before execution.
- Orchestrate multi-step campaigns with bulk ops via RUBE_REMOTE_WORKBENCH.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Verify RUBE_SEARCH_TOOLS responds and discover Zerobounce tools for your use case.
- Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["zerobounce"] and ensure the status is ACTIVE before executing tools with RUBE_MULTI_EXECUTE_TOOL (include memory).
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Verify and wait for ACTIVE status in RUBE_MANAGE_CONNECTIONS before running tools.
- Use exact field names and types from the search results.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and paginate responses if needed.
Example Use Cases
- Discover the Zerobounce email_verification tool and run it on a batch of new signups to clean invalid addresses.
- Bulk-check deliverability for a marketing list by discovering the appropriate Zerobounce tool and executing it across the list in a single session.
- Chain steps in one session: discover tools, establish a Zerobounce connection, and run multiple verification tools sequentially.
- Update workflows safely by re-fetching tool schemas before executing any tool to adapt to changes.
- Use RUBE_REMOTE_WORKBENCH to run multiple Zerobounce tasks in bulk for large campaigns.
