Tomba is a verified n8n community node providing 30+ operations across 13 resources for email discovery, verification, enrichment, phone lookup, company search, and lead management. Supports both API Key and OAuth2 authentication.
Installation
From n8n (Recommended)
Open n8n
Open the editor and click + in the top right to open the Nodes panel.
Search for Tomba
Type "Tomba" in the search field.
Add to Workflow
Click the Tomba node to add it to your workflow.
Via Community Nodes
Go to Settings → Community Nodes
Enter n8n-nodes-tomba
Click Install
Or via npm:
Code
npm install n8n-nodes-tomba
Authentication
The Tomba node supports two authentication methods:
[Email Campaign: Bounce Event] → [Tomba: Create Flag (email, hard_bounce)] → [CRM: Tag Contact]
Lead Management
Code
[Form Submission] → [Tomba: Create Lead List] → [Tomba: Create Lead] → [Tomba: Email Verifier] → [Tomba: Update Lead (score)]
Rate Limits
Rate limits are enforced per endpoint and per plan across three dimensions: per-second (rps), per-minute (rpm), and daily. Your daily limit equals monthly_credits / 5.
Plan
Credits/mo
Per Second
Per Minute
Per Day
Free
25
1
2
5
Basic
2,500
3
50
500
Growth
5,000
5
80
1,000
Pro
20,000
8
150
4,000
Pay-as-you-go 20k
20,000
10
200
4,000
50,000+ plans
50,000+
Unlimited
Unlimited
Unlimited
Request Costs
Operation
Cost
Quota Source
Domain Search
1 credit per 10 emails
Searches
Email Finder
1 credit per email
Searches
Author Finder
1 credit per email
Searches
Email Enrichment
1 credit per email
Searches
LinkedIn Finder
1 credit per email
Searches
Email Verifier
1 credit per email
Verifications
Phone Finder
5 credits per 10 phones
Searches
Phone Validator
1 credit per phone
Searches
Reveal (Companies Search)
1 credit per 50 companies
Searches
Email Count
1 credit per domain
Email Count
Email Sources
1 credit per email
Sources
No credits are charged when Tomba cannot provide a result. Duplicate requests within 30 days are not counted again.
Handling Rate Limits in n8n
The Tomba node returns rate limit headers on every response. When you hit a 429 Too Many Requests:
n8n's built-in retry mechanism will handle retries automatically if Retry On Fail is enabled on the node
Configure Wait Between Tries to respect the Retry-After header
Use the Wait node between multiple Tomba nodes to space out requests
Upgrade your plan for higher limits — 50k+ plans have no rate limits
Performance
Recommended timeout: 120 seconds. Tomba searches run in real time against live infrastructure — response times vary with the target company's SMTP server speed, website responsiveness, and the depth of catch-all detection.
To configure timeout in n8n:
Select the Tomba node
Go to Settings → Timeout
Set to 120 seconds (or higher for Domain Search on large domains)
Best Practices
Set generous timeouts — some SMTP verifications take 30-60 seconds depending on the target mail server
Use asynchronous calls — pass the webhook_url parameter (available on Domain Search, Email Finder, Email Verifier, Author Finder, LinkedIn Finder, Phone Finder) to receive results via webhook instead of waiting synchronously
Use bulk endpoints for high-volume workflows — the Tomba API supports bulk operations for all major endpoints (up to 25,000 items per batch)
Enable Retry On Fail on the Tomba node with exponential backoff to handle transient errors and rate limits gracefully
Split large lists — process items in batches using n8n's SplitInBatches node with a Wait node between batches