An Airtable Zap can take the email from a new record, run Mailthentic's Verify Email action, and write structured evidence back to that record. Keep the Airtable record ID from the trigger and add a processing-state field so the update does not start another verification.
Recommended Airtable field structure
| Airtable field | Purpose |
|---|---|
| Address supplied to Mailthentic | |
| Verification State | Your workflow guard, such as queued or complete |
| Mailthentic Status | status |
| Reason | reason |
| Confidence Score | confidence_score |
| MX Found | mx_found |
| Provider Type | mx_provider_type |
| Catch All | is_catch_all |
| Disposable | flags.is_disposable |
| Role Based | flags.is_role |
| Result Created At | created_at |
Configure the workflow
- Trigger from a new record or a dedicated Airtable view whose records have an email and no completed result.
- Test the trigger and keep its Airtable record ID.
- Add Mailthentic Verify Email and map the Airtable Email field into
Email. - Inspect the test result, including nested flags.
- Add Airtable's update-record action. Map the record ID from step one.
- Write the selected result fields and set Verification State to complete.
Map the returned record evidence
Keep status and reason even if Airtable also calculates a local decision. Use mx_provider_type and created_at rather than unsupported aliases.
| Field | Use |
|---|---|
status | Preserve the detailed Mailthentic result, such as an invalid, risky, deliverable, or unknown status. |
reason | Keep the human-readable explanation beside the status. |
confidence_score | Store the evidence score as context, not as a delivery probability. |
syntax_valid, dns_valid, mx_found | Record the input, domain, and mail routing checks. |
mx_provider_type, mx_hosts, mx_used | Retain detected provider and MX routing evidence. |
is_catch_all | Keep catch-all uncertainty visible. |
flags.is_disposable, flags.is_role | Apply separate disposable and shared-role policies. |
smtp_connectable, mailbox_confirmed, smtp_response_code | Store SMTP evidence when the receiving server makes it available. |
created_at | Record when the verification result was created. |
Create useful Airtable views
Views are easier to audit than one opaque formula. Create separate review views for clear invalid results, disposable domains, catch-all or risky results, unknown results awaiting retry, and completed results. Base each view on stored raw fields. If you add a derived decision formula, keep the raw status and reason beside it.
Review invalid, risky, and catch-all records
Correct obvious input errors before excluding a record. Treat a known disposable domain according to the source's purpose. Catch-all does not prove a mailbox exists or does not exist, so route it for review. Unknown can reflect a temporary or provider-specific limitation and should not be silently treated as invalid. The verification status guide gives each group a practical action.
Avoid repeated verification loops
A generic updated-record trigger may see the fields written by the final step and begin again. Prefer a new-record trigger or a view that includes only records where Email is present and Verification State is blank. Remove completed records from that view by setting the state in the same update action.
Credits and testing
Each accepted Mailthentic single check uses one credit. Test with records you control: a normal address, a malformed address, and a known disposable domain. Confirm the final step updates the original record ID and changes the processing state. A formula or automation that later edits Email should deliberately clear or preserve the state according to your recheck policy.
Troubleshooting
- No records trigger: confirm the selected base, table, and view, then add a complete test record.
- A new record appears: use Update Record, not Create Record.
- The wrong record changes: map the Airtable record ID from the trigger.
- The Zap repeats: narrow the view and set Verification State in the update.
- Result fields are absent: retest Mailthentic and refresh nested output fields.
When another workflow is better
For an existing file, export it and use the bulk verifier. For higher volume, controlled retries, or product logic, use the API. The Zapier automation guide compares all four source patterns.
Prepare the Airtable automation
The Airtable template is a draft and has no public URL. Open the Mailthentic Zapier hub and build from the reviewed steps.
Ready to verify your email list?
Start free with 50 verification credits. No credit card required.
Continue in Zapier
The related template is not public yet. Open the Beta integration and build the reviewed workflow from the steps above.
Explore the Mailthentic Zapier integration