Integrations

Integrate Tomba Finder with Clay

Integrate Tomba with Clay: Complete Guide

This comprehensive guide shows how to integrate Tomba's powerful email finding and verification capabilities with Clay using the HTTP API tool. Transform your lead generation workflow with automated email discovery and validation.

Overview

Tomba's integration with Clay allows you to:

• Find emails from first name, last name, and company domain
• Verify email addresses for deliverability
• Search entire domains for all available email addresses
• Find emails from phone numbers
• Get company information and employee counts
• Enrich contact data with verification scores and sources

Integration Benefits

Feature	Benefit
Real-time Processing	Get instant results as you build your lists
High Accuracy	95%+ accuracy rate with verification scores
Bulk Operations	Process hundreds of contacts simultaneously
Cost Effective	Pay only for successful finds and verifications
Data Quality	Filter out invalid, disposable, and risky emails

Prerequisites

Before you begin, ensure you have:

• Active Clay account
• Tomba.io account with API access
• Tomba API credits available
• Basic understanding of Clay's enrichment features

Getting Your Tomba API Credentials

1. Log in to your Tomba dashboard
2. Navigate to the API section
3. Copy your:
   • API Key (Public key starting with ta_)
   • API Secret (Private key starting with ts_)

Tip: Keep your API credentials secure and never share them publicly.

Quick Setup

30-Second Setup for Email Finder

1. Add Column → Add Enrichment → Search "HTTP API"
2. Add Account with Tomba credentials
3. Configure endpoint: https://api.tomba.io/v1/email-finder
4. Map your data fields (first name, last name, domain)
5. Run and create output columns

Step-by-Step Integration

Step 1: Add HTTP API Tool

1. Open your Clay table with contact data
2. Click "Add column" button
3. Select "Add enrichment" from the dropdown
4. Type "http" in the search bar
5. Choose "HTTP API" from the results

Step 2: Configure Tomba API Connection

Add New Connection

1. Click "Add account" in the HTTP API configuration
2. Name your connection (e.g., "Tomba Email Intelligence")
3. Add the following headers:

Header Field	Value
Key:	X-Tomba-Key
Value:	[Your Tomba API Key]
Key:	X-Tomba-Secret
Value:	[Your Tomba API Secret]

4. Click "Save" to store the connection

Security Note: Clay securely stores your API credentials. They're encrypted and only used for API calls.

Step 3: Configure API Request

For Email Finder Operation

Configuration Field	Value
Method:	GET
Endpoint:	https://api.tomba.io/v1/email-finder
Response Timeout:	60000 (60 seconds)

Query Parameters

Add these query parameters by mapping to your Clay columns:

Parameter	Clay Column	Required	Description
domain	Company Domain	Yes	Company website domain
first_name	First Name	Yes	Contact's first name
last_name	Last Name	Yes	Contact's last name

Step 4: Test the Integration

1. Click "Save and run 10 rows"
2. Monitor the progress in Clay's status column
3. Check for successful responses (status code 200)
4. Review any errors and adjust configuration if needed

Step 5: Create Output Columns

Once your test runs successfully:

1. Click on any cell in the HTTP API response column
2. Hover over the data fields you want to extract
3. Click "Add as column" for each field

Recommended Output Columns

Output Field	Column Name	Description
data.email	Email Address	Found email address
data.score	Confidence Score	Accuracy score (0-100)
data.status	Email Status	valid/invalid/risky
data.sources	Source Count	Number of sources found
data.position	Position	Contact's job title
data.department	Department	Contact's department

Available Tomba Operations

1. Email Finder

Endpoint: https://api.tomba.io/v1/email-finder
Purpose: Find email addresses using first name, last name, and domain

Code
 
Query Parameters:
- domain (required): company.com
- first_name (required): John
- last_name (required): Doe

2. Email Verifier

Endpoint: https://api.tomba.io/v1/email-verifier
Purpose: Verify email address deliverability

Code
 
Query Parameters:
- email (required): john.doe@company.com

3. Domain Search

Endpoint: https://api.tomba.io/v1/domain-search
Purpose: Find all email addresses for a domain

Code
 
Query Parameters:
- domain (required): company.com
- limit (optional): 50
- department (optional): engineering
- seniority (optional): executive

4. Email Sources

Endpoint: https://api.tomba.io/v1/email-sources
Purpose: Find where an email address appears online

Code
 
Query Parameters:
- email (required): john.doe@company.com

5. Phone Finder

Endpoint: https://api.tomba.io/v1/phone-finder
Purpose: Find email addresses associated with phone numbers

Code
 
Query Parameters:
- phone (required): +1234567890

Advanced Configurations

Conditional Logic with Clay Formulas

Only Search When Domain Exists

Code
 
if({Domain} != "", {Domain}, "")

Score-Based Filtering

Create a formula column to filter by confidence score:

Code
 
if({Tomba Score} >= 80, "High Confidence",
   if({Tomba Score} >= 60, "Medium Confidence", "Low Confidence"))

Batch Processing Optimization

1. Process in batches of 100-200 rows to avoid timeouts
2. Add delays between batches using Clay's rate limiting
3. Monitor your Tomba credit usage in the dashboard
4. Use filters to avoid processing duplicate domains

Error Handling

Set up conditional columns to handle API errors:

Code
 
// Check if API call was successful
if({HTTP Status} = 200, {Email Address}, "Not Found")

// Handle rate limits
if({HTTP Status} = 429, "Rate Limited - Retry Later", {Email Address})

// Handle authentication errors
if({HTTP Status} = 401, "Check API Credentials", {Email Address})

Output Management

Data Validation Formulas

Email Format Validation

Code
 
// Validate email format
if(find("@", {Email Address}) > 0, {Email Address}, "Invalid Format")

Disposable Email Detection

Code
 
// Flag disposable emails (if using Email Verifier)
if({Email Type} = "disposable", "⚠️ Disposable", {Email Address})

Creating Composite Scores

Code
 
// Create overall lead quality score
({Tomba Score} * 0.4) +
(if({Email Status} = "valid", 40, 0)) +
(if({Source Count} > 2, 20, 0))

Best Practices

Data Quality

• Clean your input data before processing
• Remove duplicates to avoid wasting credits
• Validate domains are properly formatted
• Filter out generic email domains for B2B searches

Credit Management

• Monitor usage in your Tomba dashboard
• Use filters to target high-value prospects first
• Set up alerts for credit thresholds
• Implement retry logic for failed requests

Performance Optimization

• Use appropriate timeouts (60 seconds recommended)
• Process in smaller batches for large datasets
• Monitor success rates and adjust configurations
• Cache results to avoid duplicate API calls

Compliance & Ethics

• Respect privacy regulations (GDPR, CAN-SPAM)
• Use found emails responsibly for legitimate business purposes
• Keep records of consent and opt-outs
• Target relevant prospects to maintain sender reputation

Troubleshooting

Common Issues & Solutions

Issue: "Authentication Failed" (Status 401)

Causes:

• Incorrect API key or secret
• Expired credentials
• Wrong header format

Solutions:

1. Verify credentials in Tomba dashboard
2. Check header names are exact: X-Tomba-Key and X-Tomba-Secret
3. Regenerate API credentials if needed

Issue: "Rate Limited" (Status 429)

Causes:

• Exceeded API rate limits
• Too many concurrent requests
• Bulk processing without delays

Solutions:

1. Add delays between requests
2. Process in smaller batches
3. Upgrade your Tomba plan for higher limits

Issue: No Results Found

Causes:

• Invalid domain format
• Missing required parameters
• Incorrect name formatting

Solutions:

1. Clean domain names (remove http/https)
2. Check parameter mapping in Clay
3. Verify names are properly formatted

Issue: Timeout Errors

Causes:

• Timeout set too low
• Network connectivity issues
• Large batch processing

Solutions:

1. Increase timeout to 60-90 seconds
2. Reduce batch sizes
3. Check internet connection stability

Use Cases & Examples

Use Case 1: Sales Prospecting

Scenario: Find decision-maker emails for B2B outreach

Clay Setup:

• Input: Company domains, job titles
• Process: Use Domain Search → Filter by seniority → Verify emails
• Output: Qualified prospect list with verified emails

Use Case 2: Event Marketing

Scenario: Enrich event registration data with verified emails

Clay Setup:

• Input: Attendee names, companies
• Process: Email Finder → Email Verifier → Company Finder
• Output: Complete attendee profiles for personalized follow-up

Use Case 3: Customer Data Enrichment

Scenario: Complete customer profiles with missing email addresses

Clay Setup:

• Input: Customer names, phone numbers, companies
• Process: Email Finder + Phone Finder → Verify results
• Output: Enriched customer database

Use Case 4: Competitor Analysis

Scenario: Research competitor team composition

Clay Setup:

• Input: Competitor domains
• Process: Domain Search → Analyze departments and roles
• Output: Competitive intelligence report

Advanced Workflow Examples

Multi-Step Enrichment Workflow

Code
 
1. [Company Domain] → [Company Finder] → [Get Company Info]
2. [Domain + Job Title] → [Domain Search] → [Find Team Members]
3. [Found Emails] → [Email Verifier] → [Validate Deliverability]
4. [Verified Emails] → [Email Sources] → [Check Professional Presence]

Quality Scoring System

Create a comprehensive lead scoring system:

Code
 
// Lead Quality Score Formula
let emailScore = {Tomba Score} || 0;
let validityBonus = {Email Status} === "valid" ? 25 : 0;
let sourceBonus = Math.min({Source Count} * 5, 25);
let companyBonus = {Company Size} === "1000+" ? 20 : 10;

return emailScore + validityBonus + sourceBonus + companyBonus;

Getting Help

Resources

• 🎥 Clay Integration Tutorials
• 🆘 Tomba Support

Support Channels

• Email Support: support@tomba.io
• Live Chat: Available in Tomba dashboard

---