Your first 100,000 email verifications or 10,000 work emails found are on us.100K verifications or 10K finds, free.Sign up today

Help centerIntegrations

Use Email Finder Verifier in n8n

Step by step: call Email Finder Verifier from an n8n workflow with the HTTP Request node to verify or find emails.

n8n is a tool that links apps and runs steps for you. Each step is called a node. A chain of nodes is a workflow.

You need an API key first. See Create and manage API keys. Make one named "n8n".

  1. Add a node

    Open your workflow. Click the plus button. Search for HTTP Request and pick it.

  2. Set the method and URL

    Set Method to GET. Set URL to https://api.emailfinderverifier.com/api/v1/verify.

  3. Add the email to check

    Turn on Send Query Parameters (extra details tacked onto the URL). Click to add one. Name it email. For the value, drag in the email field from the node before.

  4. Add your key as a credential

    Set Authentication to Generic Credential Type. Pick Header Auth (a way to send a key in a header, an extra line of information sent with a request). Click to create a new credential. Set the name to X-API-Key. Paste your API key as the value. Save. A credential is a saved login that every node can reuse.

  5. Test the node

    Click Execute step. You should see verified in the output.

  6. Keep only confirmed addresses

    Add an IF node (a step that splits the path in two). Set it to check that verified is true. Keep the true path.

Many items at once

Open the HTTP Request node. Under Options, click Add option and pick Batching. Set Items per Batch to 1 and Batch Interval to 1000 (milliseconds, so 1 second). That keeps you under the rate limit (how fast you may go).

To find emails instead

Use the URL https://api.emailfinderverifier.com/api/v1/find. Add three query parameters: first_name, last_name and domain. Found emails aren't verified yet. Add a second HTTP Request node that verifies them. See Find, then verify.

Good to know

  • New accounts can send 1 request per second. A 429 error means you went too fast.
  • Use a separate API key for this tool. Then you can delete it on its own.

Still stuck? Ask us on Slack. Real people answer.

Get support

Last updated 16.11.2026