ZeroBounce
Email MarketingValidate email addresses in real time with ZeroBounce before they enter your lists. Agents verify single addresses or batches of up to 200, pull engagement activity for a contact, and monitor remaining credits and API usage to protect bounce rates and sender reputation.
What This Integration Enables
Sender reputation is an asset you build for years and burn in a week, and the burn always starts the same way: unvalidated addresses entering the list. ZeroBounce's answer is a per-address verdict, valid, invalid, catch-all, spamtrap, abuse, do_not_mail, or unknown, with sub_status detail, MX data, and typo suggestions. This connector's answer is putting that verdict inside the workflow, at the exact moment an address tries to enter your system, instead of in a quarterly cleanup job. The position here is simple: validation is not a list-cleaning task, it is an admission control. FlowRunner agents enforce it at every entry point: - Signups and form submissions are validated one at a time before any downstream tool sees them - Imported and collected lists run through batch validation, 200 addresses per request - Catch-all and unknown results get a second signal from engagement activity data before anyone decides - Credit balance is checked before large jobs, so validation never fails mid-list - API usage reports feed a running record of volume and status mix, which is itself a list-health metric Each validated email consumes one credit from a finite pool, and that economics is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) layer applies: per-signup checks run free, list-scale spends wait for a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The signup that never becomes a bounce
A new customer registers via [Shopify](/integrations/shopify). Before the address goes anywhere, the agent runs Validate Email. A valid result flows straight into [SendGrid](/integrations/sendgrid) for the welcome series. A "did you mean" suggestion (gmial.com for gmail.com) triggers a confirmation prompt instead of a doomed send. A spamtrap or abuse result is suppressed with the reason logged. The mailing list only ever contains addresses that were deliverable on the day they joined, which is the cheapest deliverability program that exists.
The event lead list, cleaned before the first send
Three hundred addresses arrive from a [Typeform](/integrations/typeform) campaign. The agent calls Get Credits, confirms the balance covers the job, and runs Validate Batch in two requests of 200 and 100. Valid results sync to [Klaviyo](/integrations/klaviyo) profiles. Invalids are dropped with their sub_status recorded. The catch-all remainder gets Get Activity Data lookups, and contacts with recent opens and clicks are promoted to the sending pool. The campaign's first send goes to a list that has already survived its bounce test.
List health as a standing report, not a postmortem
Weekly, the agent pulls Get API Usage for the trailing period and posts the status breakdown to [Slack](/integrations/slack): how many addresses entered, what percentage validated clean, and whether the invalid rate is trending up. A rising invalid share from one signup source is an early warning that a form is attracting bots or a purchased list slipped in. Get Credits rides along in the same digest, so the team sees spend and balance next to the quality data it bought.
Human-in-Loop Highlight
The costly operation on this connector is Validate Batch at list scale: every validated address consumes one credit from a finite prepaid pool, and a carelessly triggered job against a 50,000-row export spends real money that does not come back, possibly draining the balance that real-time signup validation depends on. So FlowRunner agents check Get Credits first and treat any job above a configured size as a proposal: the list source, the address count, the credits it will consume, and the remaining balance go to the list owner for approval before the bulk host is called. The other human decision is what happens to do_not_mail and abuse results, because suppressing a segment of your list is a revenue decision wearing a hygiene costume. Agents assemble the evidence per address; a person signs off on the spend and the suppression.
Agent Capabilities
5 actionsValidation
2- Validate Email Validates a single email address in real time and returns its deliverability status. The status is one of valid, invalid, catch-all, spamtrap, abuse, do_not_mail, or unknown, with a more specific sub_status. Also returns metadata such as MX records, free/role-account flags, "did you mean" typo suggestions, and optional appended firstname/lastname/gender/geolocation data. Consumes one credit per validated email.
- Validate Batch Validates up to 200 email addresses in a single request using ZeroBounce's bulk API host. Accepts an array of email/IP pairs and returns per-email validation results plus a summary of errors. Each successfully validated email consumes one credit. Use Validate Email for single lookups and this operation for high-throughput checks.
Engagement
1- Get Activity Data Returns aggregate email-engagement activity data ZeroBounce has observed for a given email address, such as the number of tracked opens, clicks, forwards, and unsubscribes and the date the activity was last seen. Useful for gauging whether a contact is active. Consumes one credit per lookup.
Account
2- Get Credits Returns the number of validation credits remaining on your ZeroBounce account. A value of -1 indicates the credit balance could not be determined (for example, an invalid API key). Use this to monitor balance before running large validation jobs.
- Get API Usage Returns a breakdown of your ZeroBounce API usage between two dates, including total validations and counts by status (valid, invalid, catch-all, spamtrap, abuse, do_not_mail, unknown) and by sub_status. Dates are inclusive and use YYYY-MM-DD format. Useful for reporting and monitoring consumption.
Frequently Asked Questions
What can FlowRunner do with ZeroBounce?
FlowRunner agents can run Validate Email, Validate Batch, and Get Credits in ZeroBounce, plus 2 more actions.
Does connecting ZeroBounce to FlowRunner require OAuth?
No. ZeroBounce connects to FlowRunner with an API key, no OAuth flow required.
Can ZeroBounce trigger a FlowRunner workflow automatically?
ZeroBounce doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with ZeroBounce
$100 in credits. No card required. Connect in minutes.