n8n Webhook Lead Verification: MailVeri for Apollo & Clay

Verify every inbound lead email with MailVeri—then route for deliverability or suppression

This n8n workflow receives lead data from a webhook, normalizes key fields, validates the lead’s email using the MailVeri Verify Mail API, and automatically sends the lead down the right path: deliverable for campaign tools or suppressed when the email is not VALID.

What this workflow does

• Ingests leads via webhook: Accepts a POST webhook request containing lead details (e.g., from Apollo or Clay).
• Extracts and normalizes fields: Pulls out and standardizes the lead’s email, first name, and company from the incoming payload.
• Verifies email deliverability with MailVeri: Sends the email address to the MailVeri Verify Mail API.
• Checks verification status: Determines whether MailVeri returns a status of VALID.
• Routes output based on the result:
  • If VALID: outputs a deliverable routing payload including the clean email and a deliverable verdict for downstream tools.
  • If not VALID: outputs a suppression payload with the rejected email and the returned status as the suppression reason.

Use cases

• When Apollo or Clay pushes leads into n8n, automatically verify deliverability before syncing to outreach platforms.
• Prevent bounces and reduce list decay by suppressing leads whose emails are not VALID.
• Standardize inbound lead fields (email, first name, company) while ensuring only verifiable addresses proceed.

Technical details

• n8n nodes: webhook, if, set, http request
• External API: MailVeri Verify Mail API (use an Authorization header with YOUR_MAILVERI_API_KEY)
• Endpoints: Use the webhook URL for the lead-ingest endpoint

Setup

• Replace YOUR_MAILVERI_API_KEY in the MailVeri HTTP request Authorization header.
• Activate the workflow and copy the webhook URL for lead-ingest.
• Configure your lead source (e.g., Apollo or Clay) to POST lead data including an email field (such as email or mail).