EmailListVerify

EmailListVerify checks email addresses in bulk and in real time. Agents verify single addresses, run asynchronous verification jobs, upload and download bulk lists, check disposable domains and blacklists, find business emails, and test inbox placement.

Verified 16 actions API key available

EmailListVerify website Platform Documentation Capability data verified 2026-08-19

A quarterly hygiene run starts against the marketing database

Get Credit Balance reads what the account can afford before anything is spent

Upload Email List submits the addresses for bulk verification

Get Email List Progress polls until the run reports finished

Download Email List pulls the results file with the columns the flow asked for

The agent posts the status breakdown to the marketing channel, accept-all addresses called out separately

A marketing operations owner decides what happens to the addresses the API declined to judge

What This Integration Enables

Most verification services answer one question. EmailListVerify answers it several ways at very different prices, and that price spread is the reason to treat it as a workflow rather than as a lookup. A single address check and a full inbox placement test are both routes on the same API, and they are not remotely the same spend. Reading the balance before a bulk run, and knowing which operation is about to be called, is part of using this connector well rather than an afterthought.

FlowRunner agents verify one address at the door of a form, run asynchronous jobs for the addresses that greylisting makes slow, upload and poll bulk lists, re-scan the ones that came back unresolved, check a domain or an IP against blocklists, find business addresses at a domain, and test where a message actually lands across providers. The connector is built and verified against the vendor's published API, which matters here more than usual: three of these routes answer plain text rather than JSON, and one of the strings they can return means the account ran out of credits rather than that the address is bad. The connector raises that as an error instead of handing a seven-letter string to a flow as if it were a verdict.

Without FlowRunner

Hygiene as an annual panic Verification happens after a deliverability problem, not before one

Spend discovered afterward Nobody checks the credit balance until a bulk run stops halfway through

One verdict for every status Addresses that were never actually judged get purged alongside the ones that failed

With FlowRunner

Hygiene on a schedule Verification runs as a standing job, with the balance read before the spend rather than after

Cost known before the call The flow prices the run against the remaining balance and reports what it intends to consume

Unresolved is its own outcome Accept-all and unresolved addresses are separated out and routed to a person instead of a delete

Use Case Scenarios

The address is checked before it becomes a record

A form submission arrives from Typeform. Before the lead is written anywhere, the agent calls Verify Email and branches on the deliverable flag rather than on a status string. Clean addresses go straight into HubSpot with the record complete. Addresses that come back disposable, or that Check Disposable Domain confirms as throwaway, are tagged and routed to a review queue rather than deleted, because a person filling in a form with a burner address is still telling you something. Where the address resolves slowly behind greylisting, the flow uses Create Verification Job and Get Verification Job so the form response is never held open waiting for a mail server.
Quarterly hygiene with the spend read first

On a schedule, the agent pulls the mailable population out of the CRM, calls Get Credit Balance, and reports the intended run size against the remaining balance to Slack before it commits. Upload Email List starts the run, Get Email List Progress polls it, and Get Email List Info parses the vendor's pipe-delimited status route into a real object with the download links included. Download Email List returns the results file with the extra columns switched on that the analyst asked for, and the summary lands in Google Sheets next to the previous quarter's. Delete Email List retires the finished run only after the file is safely stored.
The reputation check that runs before the campaign, not after it

Before a large send, the agent calls Check Blacklists against the sending domain and the sending IP and posts the result. If nothing is listed, Create Inbox Placement Test seeds a test send and Get Inbox Placement Test reports where the message landed at each provider: inbox, a promotions category, spam, or nowhere at all. A clean verification list and a message that lands in the spam folder are different problems, and this is the pair of operations that tells them apart before the campaign goes out rather than while the team is trying to explain the open rate.

Human-in-Loop Highlight

EmailListVerify has a status the other verification services in this category do not: an address at a domain that accepts everything, where nothing was proven either way. Only a clean deliverable result sets the connector's deliverable flag, so an agent following the flag alone treats that whole group as failed. Accept-all is ordinary behavior on corporate mail servers, which means a purge run on that basis quietly deletes real customers at real employers. The agent will not make that call. It resolves what it can, groups the unresolved addresses by domain, prices the alternative with Get Credit Balance because Start Deep Scan re-verifies at a higher rate per address than the original check, and asks: "1,840 addresses came back accept-all, concentrated across 61 domains. Deep scan them at the higher per-address rate, keep them on the list, or suppress them? Deep scanning all of them consumes roughly a fifth of the remaining balance." The operations owner picks. The agent then executes the choice across the whole list in one pass, which is the part it is genuinely better at.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

16 actions

Verification

Verify Email Checks one address and returns the deliverability status with a boolean the flow can branch on. The gate at the front of a signup or an inbound lead.
Verify Email Detailed Checks one address and returns the supporting signals as well: MX record, provider, role account and free provider flags, and a name guess. Used when the decision needs more than a verdict.
Create Verification Job Starts an asynchronous check for a single address. The route to use when a mail server behind greylisting would otherwise hold a synchronous call open.
Get Verification Job Polls an asynchronous check, including the greylist flag that explains why it is taking as long as it is.

Reputation

Check Disposable Domain Answers whether a domain is a throwaway address provider. Cheap enough to run on every inbound record.
Check Blacklists Checks an IPv4 address, an IPv6 address, or a domain against many blocklists at once. The pre-send check on your own sending estate rather than on a recipient.

Discovery

Find Contact Email Returns business address candidates at a domain with a confidence score. Priced differently depending on whether the flow supplies a name or only the domain, so the search is worth narrowing first.

Bulk Lists

Upload Email List Starts a bulk run from either an array of addresses or a file URL pointing at a CSV, TXT, or XLSX file. Supplying neither is refused before the request leaves.
Get Email List Progress Polls a bulk run through its statuses until it reports finished, with the quality figure and the credits consumed.
Get Email List Info Reads the same run from the vendor's pipe-delimited route, parsed into a real object and carrying the ready-made download URLs.
Start Deep Scan Re-verifies the addresses a finished list could not resolve, at a higher rate per address than the original pass. The paid second attempt at an unresolved verdict.
Download Email List Retrieves the results file into FlowRunner file storage and returns the URL. The extra columns and the status filter are opt-in, which is how a flow gets a deliverable-only file.
Delete Email List Removes a finished list from the account. Not reversible, so flows download the results file first.

Inbox Placement

Create Inbox Placement Test Seeds a test send with a tracking code so the account can see where its mail actually arrives.
Get Inbox Placement Test Reports the outcome per provider: inbox, category, spam, or missing. The operation that separates a list problem from a reputation problem.

Account

Get Credit Balance Reads the on-demand and subscription balances. Called before a bulk run so the flow prices the work instead of discovering the limit halfway through it.

Frequently Asked Questions

What can FlowRunner do with EmailListVerify?

FlowRunner agents can run Verify Email, Verify Email Detailed, and Create Verification Job in EmailListVerify, plus 13 more actions.

Does connecting EmailListVerify to FlowRunner require OAuth?

No. EmailListVerify connects to FlowRunner with an API key, no OAuth flow required.

Can EmailListVerify trigger a FlowRunner workflow automatically?

EmailListVerify doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with EmailListVerify

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us