--- title: "Emailable Integration" description: "Verify email addresses before they enter your lists. Agents check deliverability in real time at signup, run batch verification jobs on lists up to 50,000 addresses, flag disposable, role, and accept-all addresses, and monitor remaining credits so flows pause before running out." url: https://flowrunner.ai/integrations/emailable date_modified: 2026-08-04T10:04:16-07:00 --- # Emailable [Sales Intelligence](https://flowrunner.ai/integrations/category/crm-sales) Verify email addresses before they enter your lists. Agents check deliverability in real time at signup, run batch verification jobs on lists up to 50,000 addresses, flag disposable, role, and accept-all addresses, and monitor remaining credits so flows pause before running out. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 5 actions · API key · available [Emailable website](https://emailable.com/) · [Platform Documentation](https://emailable.com/docs/api/) · Capability data verified 2026-07-27 1. A signup form submits a new email address at checkout 2. Verify Email checks the address in real time, returning state, reason, score, and quality flags 3. Deliverable addresses pass straight into the CRM and the mailing list; addresses with a did\_you\_mean correction bounce back to the form with the suggested fix 4. Undeliverable and disposable addresses are declined at the gate, before they can ever bounce 5. A monthly job runs Get Account, confirms credit headroom, then Start Batch on the full list for re-verification 6. The batch summary posts to the marketing channel: total counts by state, reason breakdown, and the risky segment listed 7. The marketing owner decides the fate of the risky segment, suppress, re-permission, or keep, because a verification score is evidence, not a verdict ## What This Integration Enables Sender reputation is an asset you build for years and burn in an afternoon, and every unverified address on your list is a small wager against it. Emailable prices that wager honestly: a verification costs a credit, a bounce costs reputation. FlowRunner agents run the arithmetic everywhere addresses enter the system: real-time checks at signup and checkout, pre-flight verification before sends, and scheduled batch cleaning up to 50,000 addresses per job, with the credit balance monitored so no workflow dies mid-batch. - Verify single addresses in real time with state, reason, 0 to 100 score, and quality flags - Catch disposable, role, free, accept-all, mailbox-full, and no-reply addresses before they enter lists - Recover mistyped signups with did\_you\_mean corrections at the form - Run asynchronous batch jobs with polling or callback delivery, and aggregate breakdowns by state and reason - Cancel in-progress batches when priorities change, keeping remaining spend - Monitor remaining credits so flows pause deliberately instead of failing ### Without FlowRunner **The list decays invisibly**: Addresses go stale, domains die, and the damage shows up as bounces mid-campaign **Typos become lost customers**: The signup that typed gamil.com never gets the receipt and never comes back **Cleaning is an annual panic**: List hygiene happens after a deliverability crisis, from a CSV, over a weekend ### With FlowRunner **Every address is checked at the door**: Real-time verification blocks undeliverable and disposable addresses at signup **Typos get caught in the moment**: The did\_you\_mean correction turns a doomed address into a recovered customer **Hygiene is a scheduled batch**: Monthly re-verification runs list-wide, and a human disposes of the risky segment deliberately ## Use Case Scenarios ### The front door that refuses bad addresses politely A new customer signs up in [Shopify](https://flowrunner.ai/integrations/shopify). Verify Email runs before the address syncs anywhere: deliverable states flow into the CRM and the welcome sequence, disposable and undeliverable states are declined with a request for a working address, and a did\_you\_mean hit returns the corrected suggestion to the form. The mailing list only ever receives addresses that can receive mail, which is the cheapest deliverability strategy that exists. ### Pre-flight verification before the big send A campaign is staged against a segment that has not been mailed in six months. Before anything sends, the agent loads the segment from [Google Sheets](https://flowrunner.ai/integrations/google-sheets), checks headroom with Get Account, and runs Start Batch. Get Batch polls until complete, then writes each address's state and score back to the sheet. Deliverable addresses proceed to the send; undeliverable ones are suppressed; the risky and unknown segments go to the marketing owner with the reason breakdown. The campaign that finally sends bounces against a clean list, and the sender score never knows the difference. ### Lead quality scoring that reads the flags Sales complains that form leads are junk. The agent adds Verify Email to the lead router and starts reading more than the state: role addresses like info@ and sales@ get tagged and routed to a slower nurture track instead of a rep's queue, free-domain addresses factor into the lead score, and accept-all domains are marked so nobody overreads a deliverable verdict from a catch-all server. The flags land on the record in [HubSpot](https://flowrunner.ai/integrations/hubspot) alongside the score, and routing rules act on evidence instead of vibes. ## Human-in-Loop Highlight Two operations in this connector spend things that do not come back. Start Batch is billed spend: a 50,000-address job consumes credits as it runs, and Cancel Batch stops the remainder but the verified portion is billed as usual, so batch size and timing are budget decisions the agent surfaces before starting, with the balance from Get Account attached. The subtler cost is the purge decision after the batch. The risky state is not a death sentence: it includes real customers on accept-all domains and mailboxes that were merely full on verification day, and a workflow that auto-deletes everything risky is quietly discarding revenue. So the agent suppresses only the unambiguous undeliverables and hands the risky segment to the marketing owner with reasons and scores itemized: "2,140 risky: 1,690 accept\_all, 300 low\_deliverability, 150 mailbox\_full. Suppress, re-permission, or keep?" The person chooses per slice. Deleting a subscriber you spent money acquiring, on a coin-flip signal, is exactly the kind of call that should cost a human click. 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 5 actions ### Verification 1 - **Verify Email** Verifies a single email address in real time and returns its deliverability state, deliverable, undeliverable, risky, or unknown, with a reason, a 0 to 100 score, quality flags including disposable, free, role, accept\_all, mailbox\_full, and no\_reply, a did\_you\_mean typo correction, and parsed domain, user, tag, MX record, and SMTP provider details. The gate at every signup. ### Batch 3 - **Start Batch** Starts an asynchronous batch verification job for up to 50,000 email addresses, returning a batch id for polling and optionally a callback URL that receives the completed results. The billed spend this page's human gate budgets. - **Get Batch** Retrieves a batch job's status and results by id, reporting processed and total counts while running. Completed batches of 1,000 or fewer return individual results inline; larger batches return a download CSV URL, alongside aggregate total\_counts and reason\_counts breakdowns. - **Cancel Batch** Cancels an in-progress batch job by id, stopping remaining verifications. Emails already verified before cancellation are billed as usual, so cancellation stops future spend without refunding past spend. ### Account 1 - **Get Account** Retrieves account information for the API key, including the owner's email address and the number of remaining verification credits. The headroom check that runs before every batch, so workflows pause deliberately instead of running dry mid-job. ## Frequently Asked Questions ### What can FlowRunner do with Emailable? FlowRunner agents can run Verify Email, Start Batch, and Get Batch in Emailable, plus 2 more actions. ### Does connecting Emailable to FlowRunner require OAuth? No. Emailable connects to FlowRunner with an API key, no OAuth flow required. ### Can Emailable trigger a FlowRunner workflow automatically? Emailable doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Emailable?** This integration exposes Emailable 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/emailable. Site index: https://flowrunner.ai/llms.txt