Actions8
Overview
The Tomba node's "Domain Status" operation checks the status of a given domain to determine if it is a webmail or disposable domain. This can be useful for validating user signups, filtering out temporary or generic email domains, and improving data quality in lead generation or contact management workflows.
Practical examples:
- Preventing users from registering with disposable or webmail addresses.
- Cleaning up mailing lists by identifying and removing entries from non-corporate domains.
- Enriching CRM data by flagging contacts using personal or throwaway email domains.
Properties
| Name | Meaning |
|---|---|
| Domain | Domain name from which you want to check. For example, "gmail.com". (Required) |
Output
The output is a JSON object containing the status information about the queried domain. While the exact structure depends on the Tomba API response, typical fields may include:
{
"domain": "gmail.com",
"webmail": true,
"disposable": false,
// ...other possible fields
}
domain: The domain that was checked.webmail: Boolean indicating if the domain is a webmail provider.disposable: Boolean indicating if the domain is a disposable/temporary email provider.
Dependencies
- External Service: Requires access to the Tomba API.
- API Key: You must configure Tomba API credentials in n8n under the name
tombaApi.
Troubleshooting
Common issues:
- Invalid or missing API key: Ensure your Tomba API credentials are correctly set up in n8n.
- Incorrect domain format: The "Domain" property should only contain the domain part (e.g., "gmail.com"), not a full email address.
- API rate limits: If you exceed your Tomba plan's quota, requests may fail.
Error messages:
error: { errors: [...] }
If "Continue On Fail" is enabled, failed executions will return an error object in the output array. Check theerrorsfield for details such as invalid domain or authentication issues.