Auto-verify Airtable lead emails with NeverBounce | General Input

Build a deterministic code workflow that automatically verifies the email on every new lead row in Airtable and writes the result back to that same row. No branching, no AI reasoning, no summarization. Just trigger, verify, update, the same way every time.

Trigger: poll Airtable for new records using the new_record event type. The user will configure which base and which table to watch (a lead-intake or signup table). The workflow fires once per new record.

Step 1. From the new Airtable record, read the email address out of the source email field (default field name: Email).

Step 2. Call NeverBounce Verify Single Email with that email address. The response includes a deliverability result code (one of valid, invalid, disposable, catchall, unknown), a verified-at timestamp, and a flags array.

Step 3. Call Airtable Update Record on the same record ID and write exactly these three fields, leaving every other field untouched:

Email Status: the NeverBounce result code as a string (valid, invalid, disposable, catchall, or unknown).
Verified At: the verified-at timestamp from the NeverBounce response, written as an ISO 8601 datetime.
Verification Flags: the flags array from NeverBounce, joined as a comma-separated string so it fits a single-line text column.

Expose these as workflow inputs so the user can wire the flow to their actual schema: the Airtable base ID, the table ID (or name), the source email field name, and the three result column names (Email Status, Verified At, Verification Flags). Default the column names to those exact strings.

Every column mapping is fixed and every step runs the same way every time. The point is to keep an Airtable lead base clean automatically so downstream views and follow-up automations can filter on deliverable addresses without anyone running manual cleanups.

Additional information

What does this prompt do?

Watches your Airtable lead or signup table for brand new rows.
Runs each new email through NeverBounce to see if it is deliverable, disposable, or dead.
Writes the verification result, the time it was checked, and any extra flags back onto the same row.
Keeps your views, segments, and follow-up automations focused on real, deliverable leads without manual cleanups.

What do I need to use this?

An Airtable base with a lead, signup, or contact table that has an email column.
A NeverBounce account with verification credits available.
Three extra columns on the table to receive the results: Email Status, Verified At, and Verification Flags.

How can I customize it?

Point it at a different table, or change which column holds the email address.
Rename the three result columns to match the naming you already use in your base.
Add a follow-up step, like a Slack ping when a lead comes back as invalid or disposable, so sales can react fast.

Frequently asked questions

What do the different result codes mean?

Valid means the inbox exists and is safe to send to. Invalid means the address is dead or malformed. Disposable is a burner or temporary address. Catchall means the domain accepts all mail, so deliverability is uncertain. Unknown means NeverBounce could not finish verifying the address.

Will this use NeverBounce credits?

Yes. Each new lead triggers one real-time verification, which uses one credit on your NeverBounce account. You can check your remaining balance at any time inside the NeverBounce dashboard.

Does this work on rows that are already in my table?

This workflow only runs on brand new rows added after it goes live. If you want to clean up rows you already have, run NeverBounce on a one-off list export, or duplicate this workflow and trigger it manually for older records.

What if my Airtable columns are named differently?

You can rename them when you set the workflow up. The workflow exposes the source email field name and the three result column names as inputs, so you can match whatever naming convention your base already uses.

Will it touch any other fields on my Airtable row?

No. It only writes to the three result columns you point it at: Email Status, Verified At, and Verification Flags. Every other field on the row stays exactly as your team or your signup form left it.