Do I need API keys to use this skill?

No. The setup uses Rube MCP as the gateway and does not require Neverbounce API keys.

How do I ensure tool schemas are current?

Always run RUBE_SEARCH_TOOLS before selecting and executing tools; schemas can change.

What if the connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check status before running workflows.

neverbounce-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Neverbounce Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/neverbounce

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Neverbounce operations through Composio's Neverbounce toolkit via Rube MCP. It orchestrates tool discovery, connection management, and execution using up-to-date schemas and a consistent session flow.

How This Skill Works

The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to fetch current schemas. Then you establish/verify a connection with RUBE_MANAGE_CONNECTIONS and finally execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, passing the proper arguments and a memory payload. Always reference the latest schemas and use a session_id to tie steps together.

When to Use It

When you need to run a Neverbounce verification using the latest tool schemas discovered via RUBE_SEARCH_TOOLS
When you must connect or re-authenticate Neverbounce in a workflow with RUBE_MANAGE_CONNECTIONS
When orchestrating a multi-step workflow that includes discovery, connection check, and tool execution
When you require pagination-safe retrieval of tool results and continuous tool discovery
When performing bulk or batch operations using RUBE_REMOTE_WORKBENCH with run_composio_tool

Quick Start

Step 1: Verify Rube MCP is available with RUBE_SEARCH_TOOLS
Step 2: Establish or confirm ACTIVE Neverbounce connection via RUBE_MANAGE_CONNECTIONS
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the returned slug and args

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Verify the Neverbounce connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution
Use exact field names and types from the search results for tool arguments
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and handle pagination tokens to fetch complete results

Example Use Cases

Discover available Neverbounce tools, connect, then run a verification tool on a new email list
Refresh tool schemas and re-run a bulk verification to reflect updated rules
Create a multi-step workflow: search tools, ensure connection, execute the tool with proper arguments
Execute multiple Neverbounce checks in sequence using a single session
Batch-run several verifications via RUBE_REMOTE_WORKBENCH for different datasets

Frequently Asked Questions

Add this skill to your agents