Bouncer
Email MarketingVerify email addresses and clean lists with Bouncer, validating single addresses in real time and large lists in batch. Agents screen addresses before a send so bounce rates never decide your sender reputation for you.
What This Integration Enables
Bouncer is built for teams who treat list hygiene as a standing operational job with a budget attached, not as a form-field check. It is the only shape in this category that gives an agent a batch it actually owns: a batch id it can poll, stop early with a credit refund for whatever was never verified, and permanently purge once the results are stored. That lifecycle matters because a hygiene run against a real marketing database is long enough that something else in the flow will want to know how it is going.
The second thing Bouncer separates is worth more than the batch machinery. Deliverability and reputation are different questions. An address can be perfectly deliverable and still be a spam trap or a serial complainer, and a verification score will never tell you that. Bouncer runs toxicity analysis as its own job, with its own list id and its own 0 to 5 rating, so an agent can hold two independent verdicts about the same address and route them to different decisions. FlowRunner connectors expose both paths, plus domain-only screening and the account credit balance, so an agent can size a run before it starts it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Quarterly list hygiene with a purge that waits
A scheduled flow pulls every address in the marketing database that has not been mailed in ninety days and submits it with Create Batch. The agent polls Get Batch Status, then downloads results with the filter set so deliverable, risky and undeliverable arrive as three separate sets. Undeliverable addresses are written back to Mailchimp as unsubscribed without argument, because a hard invalid address is not a judgment call. The risky cohort is different: those are catch-all domains and low-deliverability mailboxes where the verdict is genuinely uncertain, so the agent holds them and asks. Once the results are stored, Delete Batch purges the addresses from Bouncer so the personal data does not sit in two places.
Screening a sign-up domain before the mailbox check
A B2B sign-up form posts a work email. Before spending a mailbox verification, the agent calls Verify Domain on the domain part alone. If the domain is disposable, the sign-up is rejected at the form. If the domain is a catch-all, the agent knows in advance that a mailbox-level verdict will come back inconclusive, so it accepts the registration but tags the record in HubSpot as unverified rather than pretending to a certainty the protocol cannot give. Only domains that resolve cleanly get a Verify Email call, which keeps the credit spend on addresses where the answer will actually mean something.
Toxicity screening before a reactivation campaign
Before a win-back send, an agent submits the target audience with Create Toxicity List, polls Get Toxicity List Status, and downloads the ratings. Addresses rated 4 or 5 are the ones that can damage sending reputation. The agent does not suppress them on its own. It joins each one against billing records in Stripe so the human reviewing the list can see which flagged addresses belong to paying accounts, then posts the cohort for a decision. Whatever comes back is applied to the send audience, and the agent logs which addresses were held and why.
Human-in-Loop Highlight
The gate sits on suppression, because a toxicity rating is a claim about a person and suppression is a silent, permanent stop on every future campaign to them. Spam traps are safe to suppress. Complainers are not, because a complainer is frequently a real customer who once hit the spam button on a badly timed email and is still paying you. So when the agent finishes a toxicity run, it does not write suppressions. It posts to Slack: "Toxicity run on the reactivation audience returned 61 addresses rated 4 or 5. Of those, 9 belong to accounts with active subscriptions. Suppress all 61, suppress only the 52 with no active subscription, or review the 9 individually?" That is FlowRunner's human-in-the-loop pattern doing the thing it exists for: the agent did the work that scales, and stopped at the point where the wrong answer removes a paying customer from every list you own with no record of why.
Agent Capabilities
13 actionsReal-Time Verification
3- Verify Email Verifies one address in real time and returns a status of deliverable, risky, undeliverable or unknown, a reason code, a deliverability score, a toxicity rating, and flags for catch-all, disposable, free, role-based, disabled and full mailboxes. Used at the moment of capture, on a sign-up or checkout form, where a single answer decides whether the registration is accepted.
- Verify Email List Verifies a list of addresses through the synchronous queue and returns the full result set in one response, with no batch id to track. Used when a flow needs batch-grade accuracy without managing batch lifecycle, for example cleaning a freshly imported segment mid-workflow.
- Verify Domain Checks a domain without probing a specific mailbox, returning MX validity, catch-all behavior, disposable and free provider detection, the mail provider and a toxicity indication. Used to screen sign-up domains cheaply and to decide whether mailbox-level verification of that domain is worth the credit.
Batch Verification
5- Create Batch Submits a list for asynchronous verification and returns the batch id every other batch operation needs. Used for full-database hygiene runs, optionally with a callback URL so the flow resumes when the batch completes rather than polling.
- Get Batch Status Returns the state of a batch by id, along with timestamps, submitted quantity, duplicates removed, credits consumed and an optional breakdown of deliverable, risky, undeliverable and unknown counts. Used as the wait step in a hygiene flow and as the source of the cost figure shown to a reviewer.
- Get Batch Results Downloads the results of a completed batch as records carrying status, reason code, domain and account flags, provider, deliverability score and toxicity rating. Used with the result filter to pull one cohort at a time, so deliverable addresses build the send list and risky addresses go to review.
- Finish Batch Stops a running batch early and refunds the credits for addresses that were never verified. Used when a reviewer cancels a run mid-flight or when a credit check shows the balance will not cover the remainder.
- Delete Batch Permanently removes a batch and every address and result attached to it. Used as the data-minimization step once results are stored elsewhere. This cannot be undone, so it belongs after the write-back, never before it.
Toxicity Analysis
4- Create Toxicity List Submits addresses for asynchronous toxicity analysis, which flags spam traps, complainers and other addresses that can damage sending reputation, and returns a list id. Used before a reactivation or reengagement send, where the audience is by definition stale.
- Get Toxicity List Status Returns the processing state of a toxicity job by list id. Used as the wait step before results are downloaded.
- Get Toxicity List Results Downloads the completed job as address and rating pairs on a 0 to 5 scale where higher means greater risk. Used to build the suppression candidate list that goes in front of a person.
- Delete Toxicity List Permanently removes a toxicity job and its stored addresses and results. Used to purge personal data once the ratings have been recorded in the system of record.
Account
1- Get Available Credits Returns the verification credits remaining on the account. Used as a preflight check so a large batch is sized against the balance instead of failing partway through.
Frequently Asked Questions
What can FlowRunner do with Bouncer?
FlowRunner agents can run Verify Email, Verify Email List, and Create Batch in Bouncer, plus 10 more actions.
Does connecting Bouncer to FlowRunner require OAuth?
No. Bouncer connects to FlowRunner with an API key, no OAuth flow required.
Can Bouncer trigger a FlowRunner workflow automatically?
Bouncer doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Bouncer
$100 in credits. No card required. Connect in minutes.