Tomba icon

Tomba

Consume Tomba API
Join our community

Actions8

Overview

The Tomba node's "Email Verifier" operation verifies the deliverability of a given email address using the Tomba API. This is useful for workflows where you need to check if an email address is valid and can receive emails before sending communications, reducing bounce rates and improving email campaign effectiveness.

Practical examples:

  • Validating user-submitted email addresses during sign-up or form submissions.
  • Cleaning up mailing lists by removing undeliverable addresses.
  • Pre-checking emails before sending marketing or transactional messages.

Properties

Name Meaning
Email The email address you want to verify. Example: name@email.com

Output

The output is a JSON object containing the verification result for the provided email address. The structure typically includes fields such as:

{
  "email": "example@email.com",
  "did_you_mean": null,
  "user": "example",
  "domain": "email.com",
  "format": true,
  "deliverable": true,
  "full_inbox": false,
  "catch_all": false,
  "disposable": false,
  "free": false,
  "score": 0.98
}
  • email: The checked email address.
  • did_you_mean: Suggestion if a typo is detected.
  • user: Local part of the email.
  • domain: Domain part of the email.
  • format: Whether the email format is valid.
  • deliverable: If the email is deliverable.
  • full_inbox: If the inbox is full.
  • catch_all: If the domain has a catch-all policy.
  • disposable: If the email is from a disposable provider.
  • free: If the email is from a free provider (like Gmail).
  • score: Confidence score of deliverability.

Note: Actual fields 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.

Troubleshooting

Common issues:

  • Invalid API Key: If your credentials are incorrect or missing, the node will throw authentication errors. Ensure your Tomba API key is set up correctly in n8n.
  • Malformed Email Address: If the input email is not properly formatted, the API may return an error or indicate invalid format.
  • API Rate Limits: Exceeding Tomba's rate limits will result in errors; monitor your usage and upgrade your plan if necessary.
  • Network Issues: Connectivity problems between n8n and Tomba's servers can cause request failures.

Error handling:

  • If "Continue On Fail" is enabled, errors are returned in the output with an error field containing details.

Links and References

Discussion