--- title: "Reoon Email Verifier Integration" description: "Reoon Email Verifier checks whether email addresses are real and safe to send to. Agents verify a single address in quick or power mode, create a bulk verification task, and retrieve the results when it completes." url: https://flowrunner.ai/integrations/reoon-email-verifier date_modified: 2026-09-04T14:28:58-07:00 --- # Reoon Email Verifier [Email Marketing](https://flowrunner.ai/integrations/category/email-marketing) Reoon Email Verifier checks whether email addresses are real and safe to send to. Agents verify a single address in quick or power mode, create a bulk verification task, and retrieve the results when it completes. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 actions · API key · available [Reoon Email Verifier website](https://www.reoon.com/) · [Platform Documentation](https://reoon.com/articles/api-documentation-of-reoon-email-verifier/) · Capability data verified 2026-08-19 1. A prospect list lands in the warehouse, carrying a verified column somebody else wrote 2. Agent pulls a sample of rows across the domains the list is concentrated on 3. Create Bulk Task submits the sample, which Reoon always runs in power mode 4. Get Bulk Task Result returns the per address verdicts once the task completes 5. Agent compares each result against the inherited verdict and counts the disagreements 6. Agent posts the disagreement rate broken down by domain 7. The outreach owner decides whether the whole list gets re-verified before the sequence starts ## What This Integration Enables Reoon Email Verifier's product is not really the verdict. It is the choice between two verdicts that look identical in a spreadsheet and answer different questions. Quick mode replies in a fraction of a second and never contacts the individual mailbox, which makes it a good gate against malformed and disposable addresses on a registration form and a poor proof that anyone is home. On a healthy, well-configured domain it will call an address valid when no such mailbox exists. Power mode opens an SMTP conversation and reports whether the mailbox actually exists, is disabled, is full, or sits behind a catch all domain, and it can take from a few seconds to over a minute to say so. FlowRunner agents make that choice explicitly and then carry it forward. An agent can gate a signup with the fast mode, submit up to fifty thousand addresses as a bulk task that Reoon always runs in power mode whatever the single check is set to, and poll for the result. The [connectors](https://flowrunner.ai/concepts/connectors) FlowRunner builds are verified against each vendor's official API, so the mode distinction shows up in the flow rather than being buried in a query parameter nobody reviews. What an agent cannot decide on its own is whether an inherited verdict was worth trusting, and that is where the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step belongs. ### Without FlowRunner **Verified means nothing in particular**: A column labeled verified carries no record of which question was asked or when **Bounces arrive after the send**: The list looks clean until the first batch goes out and the reputation damage is already done **Speed and proof get confused**: A sub-second check and a full mailbox conversation are treated as the same result ### With FlowRunner **The question is recorded with the answer**: Every verdict is stored alongside the mode that produced it, so a later flow knows what it inherited **Disagreement is measured before the send**: A sample re-run in power mode gives a real number to decide on **Mode is chosen deliberately**: Signup gates use the fast check, outbound lists use the one that opens a mailbox conversation ## Use Case Scenarios ### A fast gate on the form, a slow gate on the send Two flows share one connector and use it differently. The signup flow calls Verify Email in quick mode, which is fast enough to run inline while the visitor waits, and rejects malformed and disposable addresses at the door. The outbound flow does the opposite: it batches the week's new prospects, calls Create Bulk Task, and waits. When the results come back, only the addresses power mode confirmed as real mailboxes are written into [Instantly](https://flowrunner.ai/integrations/instantly) as sequence-eligible. The catch all results go to a separate holding list, because catch all is not a verdict, it is a domain that refuses to tell you. ### Re-verifying a list before it touches a sending domain An enrichment run in [Clay](https://flowrunner.ai/integrations/clay) produces a few thousand contacts, some of which came from sources with unknown freshness. Before any of them reach a sequence, the agent submits them with Create Bulk Task and polls Get Bulk Task Result until the status moves through waiting and running to completed. The response reports how many addresses were accepted, how many duplicates were stripped, and how many were rejected for bad formatting, which is often the first honest signal that a source is worse than it looked. Verified addresses sync to [HubSpot](https://flowrunner.ai/integrations/hubspot); the rest get a note explaining why they were held rather than being silently dropped. ### A weekly hygiene pass on an aging house list Addresses go stale as people change jobs. On a schedule, an agent pulls the segment of contacts that have not opened anything in six months from [BigQuery](https://flowrunner.ai/integrations/bigquery), submits them as a bulk task, and writes the results back with the verification date. Contacts confirmed dead are suppressed, contacts confirmed live but disengaged move into a re-engagement flow, and the disabled and full mailbox results go to a person because those are two different stories about the same company. A digest lands in [Slack](https://flowrunner.ai/integrations/slack) with the counts. ## Human-in-Loop Highlight Here is the trap this connector is built around. A list arrives with a verified column, and nothing anywhere in it records which mode produced that column. If it was quick mode, then on every healthy domain in the file the word valid means only that the domain would accept mail, not that the person exists. So the agent does not treat the inherited column as an answer and it does not silently re-verify the entire list either, because a fifty thousand address bulk task is real time and real credits and the tasks queue one at a time. It samples. It runs a few hundred addresses through Create Bulk Task, compares each power mode result against the inherited verdict, and posts what it found: "Sampled 400 rows from the Q3 conference list. Power mode disagrees with the inherited verdict on 22 percent, concentrated in two domains that both accept all mail. Re-verify all 47,000 rows, or send to the confirmed subset only?" The agent produced the number. The person decides what the number is worth, because the cost of being wrong here lands on a sending domain that takes months to rebuild. 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 3 actions ### Single Verification 1 - **Verify Email** Verifies one address in either of Reoon's two modes. Quick mode answers in under half a second without contacting the individual mailbox, which suits a registration form gate against disposable and malformed addresses but is not proof of delivery. Power mode opens an SMTP conversation and reports whether the mailbox exists, is disabled, is full, or sits behind a catch all domain, taking anywhere from a few seconds to over a minute. ### Bulk Verification 2 - **Create Bulk Task** Submits up to fifty thousand addresses as one bulk verification task and returns the task identifier along with how many were accepted, how many duplicates were removed, and how many were rejected for bad formatting. Every address in a bulk task runs in power mode whatever the single check is set to, and tasks queue and run one at a time. For fewer than ten addresses the vendor asks you to use Verify Email instead. - **Get Bulk Task Result** Reads a bulk task: its status, how many addresses have been checked, the percentage complete, and the per address results once it finishes. The status runs waiting, running and completed, and can also report a missing or unreadable file. The vendor keys results by address rather than returning an array, so this action also returns them as a list a flow can iterate. ## Frequently Asked Questions ### What can FlowRunner do with Reoon Email Verifier? FlowRunner agents can run Verify Email, Create Bulk Task, and Get Bulk Task Result in Reoon Email Verifier. ### Does connecting Reoon Email Verifier to FlowRunner require OAuth? No. Reoon Email Verifier connects to FlowRunner with an API key, no OAuth flow required. ### Can Reoon Email Verifier trigger a FlowRunner workflow automatically? Reoon Email Verifier doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Reoon Email Verifier?** This integration exposes Reoon Email Verifier to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/reoon-email-verifier. Site index: https://flowrunner.ai/llms.txt