tomba-automation

Automate Tomba email verification and lead generation tasks via Rube MCP.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill tomba-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tomba-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/tomba-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill tomba-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of interacting with Tomba's API by providing a structured, agentic workflow for email verification and lead discovery.

Core Features & Use Cases

  • Automated Tool Discovery: Dynamically fetches current Tomba tool schemas to ensure compatibility.
  • Connection Management: Handles authentication and session state for Tomba toolkits.
  • Multi-Tool Execution: Supports complex workflows like bulk email verification or lead enrichment through Rube MCP.

Quick Start

Use the tomba-automation skill to search for available tools and verify the email address of a specific lead.

Frequently Asked Questions about tomba-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an email address using this skill?

First, call RUBE_SEARCH_TOOLS to identify the correct verification tool slug. Then, use RUBE_MULTI_EXECUTE_TOOL with the email address as an argument to perform the verification.

What should I do if my Tomba connection is not active?

Call RUBE_MANAGE_CONNECTIONS with the tomba toolkit parameter. If the status is not ACTIVE, follow the provided authentication link to complete the setup process.

Why must I call RUBE_SEARCH_TOOLS before executing tasks?

Tool schemas and available endpoints change frequently. Searching first ensures you use the correct arguments and slugs, preventing execution errors.

Can I reuse session IDs for multiple Tomba tasks?

Yes, you should reuse session IDs within a single workflow to maintain context. Generate a new session ID only when starting a completely different task.

What is the purpose of the memory parameter in tool execution?

The memory parameter stores state between tool calls. Always include it as an empty object {} if no specific memory is required to ensure schema compliance.