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

neverbounce-automation skill

safe

/neverbounce-automation

This skill automates Neverbounce tasks via Rube MCP, ensuring up-to-date tool schemas and secure, connected workflows.

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

# Neverbounce Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/neverbounce](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `neverbounce`
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: "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](https://composio.dev)*

Overview

This skill automates Neverbounce tasks through Composio's Neverbounce toolkit via Rube MCP. It standardizes discovery, connection checks, and execution so you can run email validation and related operations reliably from an agent workflow. Always search tools first to get current tool schemas before executing any action.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Neverbounce tool slugs and input schemas, RUBE_MANAGE_CONNECTIONS to ensure an active Neverbounce connection, and RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) to run the chosen tools. Workflows must include session handling, memory parameter, and exact schema-compliant arguments returned by the search step.

When to use it

Validate or clean email lists programmatically from an agent workflow
Integrate Neverbounce checks into onboarding, lead pipelines, or batch jobs
Automate periodic or scheduled bulk verification tasks
Build an agent that needs dynamic tool discovery and schema-safe execution
Run multi-step workflows that combine Neverbounce with other Composio toolkits

Best practices

Always call RUBE_SEARCH_TOOLS first and use the returned schemas and tool_slugs
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before attempting executions
Pass an explicit memory object to RUBE_MULTI_EXECUTE_TOOL, even if empty
Reuse session_id for a single workflow; generate new session_id for new workflows
Handle pagination in responses and follow continuation tokens until complete

Example use cases

Single-list validation: search tools → check connection → run email validation tool with schema-compliant args
Bulk cleaning: use RUBE_REMOTE_WORKBENCH with run_composio_tool() to process large files in batches
Onboard flow: validate user email during signup by discovering lightweight validation tool and executing immediately
Periodic audit: scheduled workflow that reuses a session_id and paginates through results for reporting

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required to connect.

What if a tool schema changes?

Always re-run RUBE_SEARCH_TOOLS before executing. Do not hardcode tool slugs or argument structures.