Articles on: Integrations and API

How to integrate Anymail Finder with n8n?

This guide explains how to connect Anymail Finder with n8n and use it in n8n workflows.


Estimated setup time: ~5 minutes.


1. Install the Anymail Finder node


First, install the official Anymail Finder community node:

  1. In n8n, go to Settings → Community Nodes
  2. Click Install
  3. In the Package name field, enter n8n-nodes-anymailfinder-official
  4. Click Install and wait for completion


Once installed, Anymail Finder will appear in your node list and can be added to any workflow.



2. Connect your Anymail Finder account


Next, connect your Anymail Finder account using an API key:

  1. In n8n, go to Credentials
  2. Click Create credential
  3. Search for Anymail Finder API
  4. Paste your API key (available on the Anymail Finder API settings page)
  5. Click Save


The API key is stored securely and can be reused across workflows.



3. Add the Anymail Finder node to a workflow


Now you can use Anymail Finder inside a workflow:

  1. Create a new workflow or open an existing one
  2. Click + Add node
  3. Search for Anymail Finder and select it


Every n8n workflow must start with a trigger. If you don't add one manually, n8n will automatically insert a Manual Trigger node. You can replace it later with a webhook, schedule, or another trigger.



4. Choose an action


The Anymail Finder node supports several actions. Choose based on your input data:


For details on parameters, limits, pricing, and responses, see the Anymail Finder API documentation.



5. Handle and filter the output


All Anymail Finder actions return an email_status field indicating the email reliability:

  • valid: Verified and safe to use
  • risky: Found but not fully verifiable
  • not_found (search only): No email found
  • invalid (verification only): Not deliverable


Recommended workflow logic:

Use an IF node to control how the workflow continues based on email_status:

  • Continue only with valid
  • Optionally include risky if acceptable
  • Always exclude not_found and invalid results



Need help?


If you run into issues:

Updated on: 08/01/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!