Actions8
Overview
The Tomba - Phone Finder operation allows you to find the phone number(s) associated with a given email address using the Tomba API. This is useful in scenarios where you have an email address and need to enrich your contact data with a corresponding phone number, such as for sales outreach, lead enrichment, or customer support workflows.
Practical examples:
- Enriching CRM records by adding phone numbers to contacts when only their email addresses are available.
- Automating lead qualification processes by retrieving additional contact information.
- Verifying or supplementing user profiles in marketing automation systems.
Properties
| Name | Meaning |
|---|---|
| The email address you want to find phone |
Output
The output will be a JSON object containing the phone number(s) and possibly other related information found for the provided email address. The exact structure depends on the Tomba API response, but typically includes fields such as:
{
"email": "name@email.com",
"phone": "+1234567890",
// ...other possible fields returned by Tomba
}
If no phone number is found, the response may be empty or contain an error field.
Dependencies
- External Service: Requires access to the Tomba API.
- API Key: You must configure n8n with valid Tomba API credentials (credential type:
tombaApi).
Troubleshooting
Common issues:
- Invalid or missing API key: Ensure your Tomba API credentials are correctly set up in n8n.
- No phone found for email: If the email address does not have an associated phone number in Tomba's database, the result may be empty.
- API rate limits: Exceeding Tomba's usage limits can result in errors; check your Tomba account for quota details.
Error messages:
error: { ... }: If an error occurs (e.g., invalid email format, network issue), the node will return an object with anerrorfield describing the problem. Review the error message for guidance and verify your input and credentials.