Tomba icon

Tomba

Consume Tomba API
Join our community

Actions8

Overview

This node integrates with the Tomba API to find sources on the web where a specific email address appears. The "Email Sources" operation is useful for verifying the provenance of an email address, tracking its mentions across the internet, or performing due diligence in lead generation and cybersecurity investigations.

Practical examples:

  • A sales team wants to verify if a prospect's email has been mentioned on reputable websites.
  • Security analysts check if a suspicious email address has appeared in data breaches or public forums.
  • Marketers validate the authenticity of email addresses collected from various sources.

Properties

Name Meaning
Email The email address you want to find sources for. Example: name@email.com

Output

The output is a JSON object (or array of objects) containing information about the sources where the specified email address was found. While the exact structure depends on the Tomba API response, typical fields may include:

  • source_url: The URL where the email address was found.
  • date_found: When the email was discovered at the source.
  • website_title: Title of the website/page.
  • snippet: Excerpt or context in which the email was found.

Example output:

[
  {
    "email": "john.doe@example.com",
    "sources": [
      {
        "source_url": "https://example.com/contact",
        "date_found": "2023-12-01",
        "website_title": "Contact Us - Example",
        "snippet": "For inquiries, email john.doe@example.com"
      }
    ]
  }
]

Dependencies

  • External Service: Requires access to the Tomba API.
  • API Credentials: You must configure Tomba API credentials in n8n under the name tombaApi.
  • n8n Configuration: No additional environment variables are required beyond the credential setup.

Troubleshooting

Common issues:

  • Invalid or missing API key: Ensure your Tomba API credentials are correctly set up in n8n.
  • Email not found: If the email address does not appear in any sources, the result may be empty or contain a message indicating no sources were found.
  • Rate limits: Excessive requests may trigger rate limiting by Tomba; monitor your API usage.

Error messages:

  • "error": { ... } in the output: Indicates an error occurred during the request (e.g., invalid email format, network issues). Check the error details for more information.
  • HTTP errors (e.g., 401 Unauthorized): Usually related to incorrect or expired API credentials.

Links and References

Discussion