How to Find Emails in n8n (Free Workflows Included)

Step 1: Setup

Import a Workflow into n8n

1. Download one of the available workflows.
2. Go to n8n and create a new workflow.
3. Click the menu icon (three dots in the upper right), then choose Import from file.
4. Select the downloaded workflow JSON file, like find-email-by-person.json.
5. Once imported, the workflow will appear in your editor. You can now customize and connect it.

Add Your Anymailfinder API Key

1. Log in to your account (or create an account).
2. Visit your account API page.
3. Copy your API key. If it's not visible, click on "Enable API".
4. If you're new, you can start a free 3-day trial and receive 100 credits instantly!

Add Credentials in n8n

1. In your n8n workflow double-click on the "Call Anymailfinder API" step.
2. Click on "Header Auth" and then "Create new credential".
3. Set:
   • Name: Authorization
   • Value: Paste here your Anymail Finder API Key
4. Close the modal and go back to your workflow.

Step 2: Customize the Input

The example workflows use a basic manual input node for demo purposes, but in real use cases, you'll want to connect them to dynamic sources. Here are the most practical ways to feed data into your email workflows:

• Google Sheets or Airtable: Trigger when new rows are added to a prospect list. Ideal for teams that manage leads in spreadsheets.
• Send from a form: Use tools like Tally, Typeform, or Webflow forms connected to n8n via webhook to capture new submissions and look up emails instantly.
• CRM integration: Connect HubSpot, Pipedrive, or Salesforce to automatically look up emails when new leads are added or updated.

In all cases, replace the Enter Person & Company Info node with your preferred trigger node. The rest of the workflow stays the same.

Step 3: Handle the Output

Each workflow has 4 possible outcomes after the API call. Here's how they work and what you might do with them:

1. Email Found
   When the response contains email_status: valid, it means the email is verified and safe to use. This is where you should add your next steps - like sending the contact to your CRM, writing it to Google Sheets, or starting an outreach email.
   Node name suggestion: Continue with Valid Email
2. Email Not Found or Risky
   If email_status is not_found or risky, the email may not be reliable. You can choose to skip it, flag it, or send to a "manual review" list depending on your workflow.
   Node name suggestion: Handle Invalid or Missing Email
3. Bad Input (400 Error)
   If the request fails due to missing or invalid input (like no name or domain), the workflow will continue (not stop), and you can log that row for review later. This ensures one bad row won't stop the whole batch.
   Node name suggestion: Log Invalid Input (400 Error)
4. Auth or Credits Error (401/402)
   These errors are critical: either the API key is missing/invalid, or your account has no credits. In this case, the workflow stops immediately and shows a clear error in the UI so you can fix the issue.
   Node name suggestion: Stop on Auth or Credits Error

This structure gives you full control, even when handling many rows from Google Sheets, Airtable, or CRM data. You can safely scale without losing visibility or breaking workflows.

Understand Email Statuses

Every email lookup returns a status that indicates whether the email is safe to use. Here's what the statuses mean:

• valid: Verified and safe to send. Use this email in your outreach.
• risky: Might bounce - typically because it couldn't be verified, even though it may exist. Use with caution.
• not_found: No email was found for that person or company.
• blacklisted: The email is on a suppression list or not allowed for legal/compliance reasons.

In our default workflow, the Switch node checks email_status and splits into 3 paths:

• valid → Connected to Email Found
• risky → Treated the same as not found and connected to Email Not Found
• not_found → Also goes to Email Not Found

If you want to include risky emails in your main results (for example, to do outreach to them anyway), you can simply change the workflow so that the risky output is connected to the same node as valid. Just drag the line to the "Email Found" path.

Note: Risky emails are returned for free - they don't cost you credits. So you can safely ignore them without wasting anything.

However, use caution: risky emails may bounce, so it's best to monitor delivery or use separate campaigns if you decide to use them.

Need Help?

If you have any questions or need support:

• Chat with us directly - open live chat
• Email our team at team@anymailfinder.com

We're here to help you get the most out of your workflow automation.