Verifi.Email
Email MarketingValidate single addresses or whole lists in real time with Verifi.Email, returning a deliverability verdict with supporting detail. Agents clean a list before a send rather than after a bounce.
What This Integration Enables
Three operations is a position, not a gap. Verifi.Email splits deliverability along the line that actually causes mail to fail and refuses to blur it: is the recipient real, and is your domain authorized to speak for itself. Most services in this category answer only the first and leave the second to a DNS console nobody opens between incidents.
On the recipient side, the verdict comes back as an overall answer plus a breakdown of the individual checks that produced it: RFC syntax compliance, valid MX record, spoof-free status, disposable-address detection, and the detected mailbox provider. That shape lets an agent branch on the reason rather than on a single score. List validation is synchronous and returns one result per address in submitted order, so a whole imported segment can be cleaned inside a flow with no batch id, no polling loop and no state to reconcile if the flow restarts. On the domain side, Check Domain Health returns a scored audit across SPF, DKIM, DMARC and BIMI with the published records, the active policy and an actionable recommendation per protocol. That turns sender authentication from a thing you configured once into something a flow can watch.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Cleaning an imported list inside the flow
A partner sends over a list of event registrants as a spreadsheet. The agent reads it from Google Sheets, splits it into chunks that respect the plan rate limit, and runs each chunk through Validate Email List. Results come back in submitted order, so the agent can zip them straight back onto the source rows without a join key. Addresses failing the MX check are dropped, disposable addresses are dropped, and everything else is written into Klaviyo with the detected mailbox provider stored as a property so segmentation can treat consumer and corporate mailboxes differently. The whole thing runs in one pass with no batch state to resume.
Gating record creation on a real address
An inbound lead form posts to the flow. Before a CRM record exists, the agent calls Validate Email. A failed syntax or MX check means the address cannot receive anything, so the lead is held in a review queue rather than written to Salesforce where it would dilute conversion reporting and sit in a nurture sequence forever. A spoof-free failure is treated differently: it is escalated rather than dropped, because an address that looks spoofed on an inbound form is a signal about the submission, not just about the mailbox.
Monthly authentication audit with movement tracking
A scheduled flow runs Check Domain Health across every sending domain and stores the total score and each protocol block. The agent compares against the previous run and only speaks up when something moved. If DMARC still reports a p=none policy three months running, it says so with the recommendation attached. If DKIM stopped publishing after an infrastructure change, that is raised as an incident in Jira with the previous and current records side by side, because that one silently breaks authentication for every message the domain sends.
Human-in-Loop Highlight
The gate is on acting on a recommendation. Check Domain Health will tell you, correctly, that a DMARC policy of p=none should be tightened to quarantine or reject. Publishing that change is a DNS edit with a blast radius nobody can see from inside the deliverability tool. Tightening DMARC starts silently rejecting mail from every sender that is not aligned, and in a mid-sized company that list always includes something forgotten: the invoicing system, the applicant tracking tool, a regional office relaying through its own server. So the agent does not touch DNS. It assembles the case and asks: "Check Domain Health scores example.com at 62 against a target of 100. DMARC is published at p=none and the recommendation is p=quarantine. SPF currently authorizes six sending sources. I can see traffic from four of them in the last thirty days. Publish the change, publish it with pct=25 first, or hold until the two unrecognized sources are identified?" The agent brought the evidence to the person who knows what else sends as that domain. That person makes the call, and the flow records who approved the change and when.
Agent Capabilities
3 actionsEmail Validation
2- Validate Email Validates one address in real time and returns an overall deliverability verdict plus a breakdown of the individual checks: RFC syntax compliance, valid MX record, spoof-free status, disposable-address detection and the detected mailbox provider. Used at the point of collection so an undeliverable address never becomes a CRM record, and so the flow can branch on the specific check that failed rather than on a single verdict.
- Validate Email List Validates a list of addresses in one synchronous request and returns one result object per address in the same order they were submitted. Used to clean an imported list or a set of migrated contacts inside a single flow step, with the ordering guarantee removing the need for a join key on the way back.
Domain Health
1- Check Domain Health Assesses the email authentication health of a sending domain and returns a total score against its target plus a per-protocol breakdown for SPF, DKIM, DMARC and BIMI. Each block reports its score and target, whether records are published, the published records themselves, the active policy where one applies, and a recommendation. Used for scheduled authentication audits and for catching the day a DNS change quietly weakens a protocol.
Frequently Asked Questions
What can FlowRunner do with Verifi.Email?
FlowRunner agents can run Validate Email, Validate Email List, and Check Domain Health in Verifi.Email.
Does connecting Verifi.Email to FlowRunner require OAuth?
No. Verifi.Email connects to FlowRunner with an API key, no OAuth flow required.
Can Verifi.Email trigger a FlowRunner workflow automatically?
Verifi.Email doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Verifi.Email
$100 in credits. No card required. Connect in minutes.