NeverBounce

Verify email addresses before they hurt deliverability: agents check a single address in real time, run bulk NeverBounce verification jobs over whole lists, poll job progress, and pull per-email results with typo corrections and remaining credit balances.

7 actions API key available

NeverBounce website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A raw contact list lands for an upcoming campaign

Get Account Info checks the remaining credit balance against the list size

Create Job stages the bulk verification with Auto Start off, each row carrying its record ID for correlation

Start Job runs a sample of the list first

Agent reads the sample's result breakdown from Get Job Status, the valid rate, the catchall share, the bad-syntax count

The list owner sees the sample quality and the credit cost of the full run, and decides to proceed, fix the source, or stop

Start Job processes the full list once approved, and Get Job Results pages the outcomes back

The cleaned list, the discard pile, and the credits spent post to the team channel

What This Integration Enables

Sender reputation is an asset you spend every time you email an address that does not exist, and no amount of copywriting buys it back. NeverBounce is the checkpoint: every address comes back valid, invalid, disposable, catchall, or unknown, with flags and typo corrections attached. What FlowRunner adds is placement, putting that checkpoint inside the flows where addresses actually enter and leave your systems, instead of in a standalone tool someone visits twice a year. - Validate addresses at signup, before they enter the CRM or the mailing list - Clean whole lists in bulk before a campaign, one credit per email, sample first - Filter disposable, role, catchall, and invalid addresses ahead of outreach - Catch likely typos with suggested corrections on single verifications - Monitor remaining credits before committing to a large verification run Verification costs credits and its verdicts are not all binary, which is why FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step sits at the two places judgment enters: the spend and the grey zone.

Without FlowRunner

Lists go out unverified The campaign sends to whatever the CRM contains, and the bounce report writes the post-mortem

Cleaning is an occasional project Someone exports, uploads to a cleaning tool, downloads, re-imports, twice a year at best

Verification spend is invisible Credits get consumed with nobody tracking what a run cost or whether the list deserved it

With FlowRunner

Verification is a pipeline stage Every address passes through a real-time check or a bulk job before anything downstream sends to it

Cleaning runs continuously Signups verify at the door, and lists verify in bulk before every major send, sample first

Spend is checked before it happens Balance and list size meet in a gate, and a person approves the burn on large runs

Use Case Scenarios

The signup that gets corrected at the door

A [Typeform](/integrations/typeform) submission arrives. The agent runs Verify Email on the address: valid entries pass through to the CRM and the mailing list, invalid and disposable ones are held, and when NeverBounce returns a suggested correction, gmial.com for gmail.com, the flow uses the corrected address and logs the fix. The list grows one verified address at a time, and the typo that would have been a permanent dead record becomes a working subscriber.

The pre-campaign clean that pays for itself

Before the quarterly send, the agent pulls the list from [Google Sheets](/integrations/google-sheets), stages it with Create Job, and runs the sample-and-approve gate. On approval the full job runs, and Get Job Results pages back every outcome, correlated to source rows by the ID each entry carried in. Valid addresses write back to the clean tab, invalid ones route to a suppression tab, and the summary posts to [Slack](/integrations/slack). The campaign sends to a list that earned its send.

Prospecting that only pushes real addresses

Prospects surface from [Apollo](/integrations/apollo-io). The agent verifies each address with Verify Email before it reaches the outreach tool, and the flags do extra duty: role accounts get routed to a lower-intensity sequence, free-host addresses inform lead scoring, and only clean, deliverable addresses enter the primary cadence in [Smartlead](/integrations/smartlead). The sales team's domain reputation stops subsidizing the data vendor's error rate.

Human-in-Loop Highlight

Start Job is where this connector spends money that does not come back: bulk verification burns one credit per email, drawn from the finite balance Get Account Info reports, and a 60,000-row job started carelessly is 60,000 credits gone whether the list deserved verification or was garbage a source-level fix would have caught. So FlowRunner flows stage every large job in a waiting state and run the sample first. The gate shows the list owner two things machine logic cannot weigh alone: the cost, "58,400 remaining credits, this job consumes 41,200," and the sample verdict, "sample of 500: 62 percent valid, 21 percent catchall, 9 percent bad syntax." That catchall number is the second judgment call, because catchall domains accept everything and verification cannot promise delivery; whether those addresses are worth mailing is a risk decision about your sender reputation, not a data lookup. The person approves the burn and sets the catchall policy; the agent executes both and logs what was spent and why.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

7 actions

Verification

Verify Email Verifies one address in real time, returning valid, invalid, disposable, catchall, or unknown, plus detection flags, an optional suggested typo correction, parsed address components, and the remaining credit balance. Consumes one credit.

Bulk Jobs

Create Job Creates a bulk verification job from an array of email entries, each with optional ID and name for correlating results to source records. Auto Start runs immediately; leaving it off stages the job for the approval gate. One credit per email once running.
Start Job Starts a waiting job, optionally verifying only a sample of the list first. The operation this page's human gate exists for on full runs.
Get Job Status Retrieves a job's status and percent complete with a result breakdown: valid, invalid, catchall, disposable, unknown, duplicates, and bad syntax. The polling read that feeds the sample verdict.
Get Job Results Retrieves a completed job's per-email results, paginated, each with original data, outcome, and flags. The read that routes every address to keep, correct, or suppress.
List Jobs Lists bulk jobs, most recent first, with ID, filename, status, and record counts. The audit trail of what has been verified and when.

Account

Get Account Info Retrieves remaining paid and free credits and job counts by status. The balance check that runs before any large job is staged.

Frequently Asked Questions

What can FlowRunner do with NeverBounce?

FlowRunner agents can run Verify Email, Create Job, and Start Job in NeverBounce, plus 4 more actions.

Does connecting NeverBounce to FlowRunner require OAuth?

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

Can NeverBounce trigger a FlowRunner workflow automatically?

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

Start building with NeverBounce

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us