Rows.com Integration
Rows.com is a powerful online spreadsheet platform that supports HTTP API integrations, making it perfect for connecting with Tomba.io's email intelligence services. This integration allows you to enrich your data directly within spreadsheets using Tomba's email finding, verification, and enrichment capabilities.
Overview
With this integration, you can:
- Find email addresses for contacts directly in your spreadsheets
- Verify email deliverability for existing contact lists
- Enrich contact data with additional information
- Discover company emails by searching domains
- Validate phone numbers and find contact details
- Automate data enrichment workflows within your spreadsheets
Prerequisites
Before you begin, ensure you have:
- Rows.com account: Sign up at rows.com
- Tomba.io API key: Get your API key from Tomba.io Dashboard
- Basic HTTP knowledge: Understanding of REST API concepts
Authentication Setup
1. Get Your Tomba.io API Key
- Log in to your Tomba.io Dashboard
- Navigate to API → API Keys
- Copy your API Key and Secret Key
- Keep these credentials secure
2. API Authentication Format
Tomba.io uses custom header authentication. In Rows.com, you'll use the PAIR2JSON() function to create the proper headers:
Code
For more information about API authentication in Rows, see Authenticating your API calls.
Core Integrations
1. Email Finder
Find email addresses for individuals using their name and company domain.
HTTP Request Setup in Rows
Code
Spreadsheet Setup
| A (First Name) | B (Last Name) | C (Domain) | D (Email Result) |
|---|---|---|---|
| John | Smith | example.com | =GET(...) |
| Jane | Doe | company.co | =GET(...) |
Extract Email from Response
Code
2. Email Verifier
Verify the deliverability of email addresses.
HTTP Request
Code
Extract Verification Status
Code
Spreadsheet Layout
| A (Email) | B (Response) | C (Status) | D (Score) |
|---|---|---|---|
| john@example.com | =GET(...) | =JSON_EXTRACT(B2, "$.data.result") | =JSON_EXTRACT(B2, "$.data.score") |
3. Domain Search
Find all email addresses associated with a domain.
HTTP Request
Code
Extract Email Count
Code
4. Email Enrichment
Enrich existing email addresses with additional data.
HTTP Request
Code
Extract Enrichment Data
Code
Advanced Use Cases
1. Bulk Email Finding Workflow
Create a comprehensive contact discovery system:
Setup Columns:
- A: Company Name
- B: Domain
- C: First Name
- D: Last Name
- E: Email Finder Response
- F: Found Email
- G: Verification Response
- H: Email Status
Formulas:
Email Finder (Column E):
Code
Extract Email (Column F):
Code
Verify Email (Column G):
Code
Email Status (Column H):
Code
2. Lead Qualification Pipeline
Build a complete lead research and qualification system:
Columns Setup:
- A: Company Domain
- B: Domain Search Response
- C: Total Emails
- D: Company Enrichment Response
- E: Company Name
- F: Industry
- G: Employee Count
- H: Technologies
Domain Analysis:
Code
Extract Company Data:
Code
3. Contact List Cleanup
Clean and enrich existing contact databases:
Setup:
- A: Original Email
- B: Verification Response
- C: Status
- D: Score
- E: Enrichment Response
- F: Full Name
- G: Company
- H: Position
Verification:
Code
Enrichment (only for valid emails):
Code
Error Handling
Common Error Responses
Handle API errors gracefully in your formulas:
Code
Rate Limiting
For rate limiting, Rows.com doesn't have a built-in WAIT function, but you can implement delays by:
- Spreading requests across different time periods
- Using conditional formulas to avoid simultaneous calls
- Implementing manual refresh strategies
Data Validation
Validate inputs before making API calls:
Code
Best Practices
1. Optimize API Usage
- Batch requests when possible
- Cache responses to avoid duplicate calls
- Implement error handling for failed requests
- Monitor rate limits and API usage
2. Data Management
- Clean input data before processing
- Validate email formats before verification
- Store raw responses for future reference
- Create summary statistics for analysis
3. Performance Tips
- Use conditional formulas to avoid unnecessary API calls
- Implement progressive enrichment (verify before enriching)
- Create separate sheets for different data types
- Use named ranges for API credentials
Sample Templates
1. Basic Email Finder Template
| Column | Purpose | Formula |
|---|---|---|
| A | First Name | Manual input |
| B | Last Name | Manual input |
| C | Domain | Manual input |
| D | API Response | =GET(CONCATENATE("https://api.tomba.io/v1/email-finder?first_name=", A2, "&last_name=", B2, "&domain=", C2), PAIR2JSON("X-Tomba-Key", "YOUR_API_KEY", "X-Tomba-Secret", "YOUR_SECRET_KEY")) |
| E | Found Email | =PARSE(D2, "data.email") |
| F | Confidence | =PARSE(D2, "data.score") |
2. Email Verification Template
| Column | Purpose | Formula |
|---|---|---|
| A | Email Address | Manual input |
| B | Verification Response | =GET(CONCATENATE("https://api.tomba.io/v1/email-verifier?email=", A2), PAIR2JSON("X-Tomba-Key", "YOUR_API_KEY", "X-Tomba-Secret", "YOUR_SECRET_KEY")) |
| C | Status | =PARSE(B2, "data.result") |
| D | Score | =PARSE(B2, "data.score") |
| E | Reason | =PARSE(B2, "data.reason") |
3. Domain Research Template
| Column | Purpose | Formula |
|---|---|---|
| A | Domain | Manual input |
| B | Search Response | =GET(CONCATENATE("https://api.tomba.io/v1/domain-search?domain=", A2), PAIR2JSON("X-Tomba-Key", "YOUR_API_KEY", "X-Tomba-Secret", "YOUR_SECRET_KEY")) |
| C | Total Emails | =PARSE(B2, "meta.total") |
| D | Company Name | =PARSE(B2, "data.domain.company_name") |
| E | Industry | =PARSE(B2, "data.domain.industry") |
Troubleshooting
Common Issues
Authentication Errors:
- Verify API key and secret are correct
- Check header formatting
- Ensure API key has proper permissions
Rate Limit Exceeded:
- Implement delays between requests
- Reduce concurrent API calls
- Upgrade your Tomba.io plan if needed
Invalid Responses:
- Validate input data format
- Check for required parameters
- Handle empty or null values
Network Errors:
- Check internet connectivity
- Verify Tomba.io service status
- Implement retry logic for failed requests
Debugging Tips
- Test API calls manually using tools like Postman
- Start with simple requests before building complex workflows
- Log responses to understand data structure
- Use conditional logic to handle edge cases
- Monitor API usage in your Tomba.io dashboard
Security Considerations
- Never expose API keys in shared spreadsheets
- Use environment variables or secure storage for credentials
- Implement proper access controls for sensitive data
- Regularly rotate API keys for security
- Monitor API usage for suspicious activity
Pricing and Limits
- Check your Tomba.io plan limits
- Monitor usage in the Tomba.io Dashboard
- Consider upgrading for higher rate limits
- Implement efficient caching to minimize API calls
Next Steps
- Learn more about getting data from APIs in Rows
- Understand API authentication in Rows
- Explore Tomba.io API Documentation
- Learn about rate limits and quotas
- Understand API authentication
- Review data attributes and formats
This integration enables powerful data enrichment workflows directly within Rows.com, making it easy to build comprehensive contact research and lead generation systems using familiar spreadsheet interfaces.