Actions8
Overview
The Tomba node's "Email Finder" operation is designed to generate or retrieve the most likely email address for a person at a given domain, based on their first and last name. This is particularly useful for sales, marketing, or recruitment professionals who need to contact individuals at specific companies but do not have their direct email addresses.
Practical examples:
- A recruiter wants to reach out to a potential candidate at "stripe.com" and knows their name.
- A salesperson is prospecting leads and needs to find the best guess for an executive's email at a target company.
- A marketer is building a list of contacts for outreach campaigns.
Properties
| Name | Meaning |
|---|---|
| Domain | Domain name from which you want to find the email addresses. For example, "stripe.com". |
| First Name | The person's first name. It doesn't need to be in lowercase. |
| Last Name | The person's last name. It doesn't need to be in lowercase. |
Output
The output is a JSON object containing the result from Tomba's /email-finder API endpoint. Typical fields may include (but are not limited to):
{
"email": "john.doe@stripe.com",
"first_name": "John",
"last_name": "Doe",
"domain": "stripe.com",
"score": 95,
"sources": [
{
"uri": "https://example.com/source",
"extracted_on": "2023-01-01"
}
],
"accept_all": false,
"status": "valid"
}
email: The found or generated email address.first_name,last_name,domain: Echoes the input values.score: Confidence score for the guessed email.sources: Array of sources where this email was found (if any).accept_all: Indicates if the domain accepts all emails.status: Verification status of the email.
Note: The actual structure may vary depending on the Tomba API response.
Dependencies
- External Service: Requires access to the Tomba API.
- API Key: You must configure Tomba API credentials in n8n under the name
tombaApi. - n8n Configuration: No additional configuration required beyond setting up credentials.
Troubleshooting
Common Issues:
- Invalid or missing API key: Ensure your Tomba API credentials are correctly set in n8n.
- Insufficient input data: All three properties (Domain, First Name, Last Name) are required; missing any will cause errors.
- No email found: If Tomba cannot find or generate an email, the response may be empty or contain a low confidence score.
Error Messages:
error: { ... }in the output: Indicates an error occurred during the request. Check the error details for more information.- HTTP errors (e.g., 401, 403): Usually indicate authentication issues—verify your API key.
- 400 Bad Request: Likely due to missing or invalid input parameters.