Actions5
- Company Email Actions
- Decision Maker Actions
- Email Verification Actions
- LinkedIn Email Actions
- Person Email Actions
Overview
This node integrates with the Anymailfinder API to find and verify email addresses related to companies and individuals. Specifically, the "Company Email" resource with the "Find Emails" operation allows users to retrieve up to 20 email addresses associated with a given company domain or name. This is useful for sales, marketing, recruitment, or any scenario where you need to gather contact emails from a specific company.
For example, a user can input the domain "microsoft.com" or the company name "Microsoft" to get a list of emails found at that company. This helps automate lead generation or enrich contact databases without manual searching.
Properties
| Name | Meaning |
|---|---|
| Domain | Company domain (e.g., "microsoft.com"). Use either domain or company name. |
| Company Name | Company name (e.g., "Microsoft"). Domain is preferred for better accuracy. |
| Additional Options | Optional settings: • Webhook URL: URL to receive webhook callback when result is ready (instead of waiting synchronously). • Timeout (Seconds): Request timeout in seconds; recommended default is 180 seconds for searches. |
Output
The node outputs a JSON array containing the results returned by the Anymailfinder API for the company emails search. Each item in the array represents an email record found at the specified company, typically including details such as the email address and possibly metadata about the confidence or source.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Anymailfinder service.
- The node makes HTTP POST requests to
https://api.anymailfinder.com/v5.1/find-email/company. - Optional webhook URL support for asynchronous callbacks.
- Recommended to configure appropriate request timeout (default 180 seconds).
Troubleshooting
- Missing Domain or Company Name: The node requires at least one of these properties to be provided. If both are empty, it throws an error indicating that one must be supplied.
- Timeouts: Searches may take time; if the request times out, consider increasing the timeout value in additional options.
- API Authentication Errors: Ensure the API key credential is correctly configured and valid.
- Webhook URL Issues: If using webhook callbacks, ensure the URL is publicly accessible and can handle incoming POST requests.
- Rate Limits or Quotas: The API may limit the number of requests or emails returned; check your account limits if results are incomplete or errors occur.
Links and References
- Anymailfinder API Documentation (for detailed API usage and parameters)
- n8n Documentation on Credentials (for setting up API keys)