Overview
The Tomba Contact Intelligence skill on ClawHub gives AI agents access to Tomba's full suite of contact discovery, email verification, lead enrichment, phone lookup, and company research tools. It uses the Tomba MCP server under the hood and guides the agent to pick the right tools and multi-step workflows automatically.
Prerequisites
- Active Tomba.io account with API credentials
- ClawHub account with OpenClaw access
- Tomba MCP server connected in the session
Setup & Authentication
Install the Skill
Install the skill from ClawHub:
Code
Or copy the skill folder into your skills directory:
Code
Environment Variables
Set your Tomba API credentials:
- TOMBA_API_KEY (required) — Your Tomba.io API key
- TOMBA_SECRET_KEY (required) — Your Tomba.io secret key
Getting Your API Credentials:
- Log in to your Tomba.io dashboard
- Navigate to API Keys
- Copy your API Key and Secret Key
Connect the Tomba MCP Server
Make sure the Tomba MCP server is connected in your OpenClaw session. The skill expects the following 12 tools to be available:
domain_searchemail_finderemail_verifieremail_enrichmentauthor_finderlinkedin_finderphone_finderphone_validatoremail_countsimilar_findertechnology_findercompanies_search
Available Tools
Email Finder
Find a professional email address using a person's name and company domain.
Input Fields:
- Domain (required) — Company domain (e.g.,
tomba.io) - First Name (required) — Person's first name
- Last Name (required) — Person's last name
Output:
- Email address
- Confidence score
- Position and department
- Sources
- Verification status
Email Verifier
Verify if an email address is valid and deliverable.
Input Fields:
- Email (required) — Email address to verify
Output:
- Email status (valid/invalid)
- Result (deliverable/undeliverable/risky/unknown)
- Score (0–100)
- SMTP check results
- Disposable and free provider detection
Email Enrichment
Expand an existing email into richer contact and company data.
Input Fields:
- Email (required) — Email address to enrich
Output:
- Full name, position, department
- Company details
- Social profiles
- Location data
Domain Search
Find all known email addresses associated with a company domain.
Input Fields:
- Domain (required) — Company domain (e.g.,
stripe.com)
Output:
- List of email addresses
- Name, position, department per contact
- Sources and last seen dates
Phone Finder
Find phone numbers from an email, domain, or LinkedIn profile.
Input Fields:
- Email (optional) — Email address
- Domain (optional) — Company domain
- LinkedIn (optional) — LinkedIn profile URL
Output:
- Phone numbers
- Phone type (mobile/landline)
- Country and carrier info
Phone Validator
Validate a phone number and return carrier details.
Input Fields:
- Phone (required) — Phone number to validate
- Country Code (optional) — ISO country code
Output:
- Valid/invalid status
- Carrier name
- Line type
- Country and location
LinkedIn Finder
Find an email address from a LinkedIn profile URL.
Input Fields:
- URL (required) — LinkedIn profile URL
Output:
- Email address
- Confidence score
- Profile data
Author Finder
Find the contact email of an article author.
Input Fields:
- URL (required) — Article URL
Output:
- Author email address
- Confidence score
- Author name
Email Count
Estimate the number of known email addresses for a domain.
Input Fields:
- Domain (required) — Company domain
Output:
- Total email count
- Personal vs generic breakdown
- Department distribution
Technology Finder
Identify the website technology stack for a domain.
Input Fields:
- Domain (required) — Company domain
Output:
- Detected technologies by category
- CMS, analytics, frameworks, hosting, etc.
Similar Finder
Find similar or competing domains.
Input Fields:
- Domain (required) — Company domain
Output:
- List of similar domains
- Domain metadata
Companies Search
Find companies using structured market filters.
Input Fields:
- Query (optional) — Natural language search query
- Country (optional) — Country codes (e.g.,
US,FR) - Industry (optional) — Industry filter
- Size (optional) — Employee count range (e.g.,
51-250) - Revenue (optional) — Revenue range
Output:
- Company name and domain
- Industry, size, location
- Revenue and employee data
Common Workflows
Find a Person's Best Email
Code
Enrich an Existing Lead
Code
Research a Company for Outreach
Code
Build a Target Account List
Code
Find Contact from LinkedIn
Code
Example Prompts
Contact Discovery
- "Find the best partnerships contact at stripe.com"
- "Guess and verify the email for Jane Doe at Acme"
- "Find the author email for this blog post: https://example.com/article"
Lead Enrichment
- "Enrich this lead and check whether a phone number is available: jane@acme.com"
- "Use this LinkedIn profile to find an email: https://www.linkedin.com/in/example"
Company Research
- "Research tomba.io for contact coverage, technology stack, and similar competitors"
- "Find software companies in France with 51-250 employees and revenue between $10M-$50M"
- "Show me companies similar to notion.so"
Output Standards
The skill instructs the agent to:
- Distinguish clearly between confirmed data and inferred data
- State whether an email was verified
- Include the source input used for each lookup
- Keep summaries concise and decision-oriented
- Suggest the next best lookup path if no high-confidence result is found
Troubleshooting
Skill Not Detected
- Confirm the skill folder exists in your OpenClaw skills directory
- Restart the OpenClaw gateway or start a new session
- Check that
SKILL.mdis present in the skill folder
Tools Not Available
- Verify the Tomba MCP server is connected in your session
- Check that
TOMBA_API_KEYandTOMBA_SECRET_KEYare set - Confirm all 12 Tomba tools are registered in the MCP server
Low Confidence Results
- Provide more specific input (full name, exact domain, LinkedIn URL)
- Use
email_verifierto validate results before acting on them - Try
domain_searchas a fallback whenemail_finderreturns low scores
Best Practices
- Always verify emails with
email_verifierbefore using them for outreach - Provide the most specific input available — full name plus exact company domain yields the best results
- Use
companies_searchto build targeted lists before drilling into individual contacts - Chain tools together: find → verify → enrich for the most complete profiles
- Check
email_countbeforedomain_searchto gauge how many contacts are available
API Limits
API limits depend on your Tomba.io subscription plan. See Usage and Quotas for details.
Resources
Support
- Tomba.io Support: help.tomba.io
- ClawHub Issues: clawhub.ai
- MCP Server Issues: GitHub Issues