NeverBounce provides email verification services to ensure the validity of email addresses, enhancing deliverability and reducing bounce rates.
NeverBounce provides email verification services to ensure the validity of email addresses, enhancing deliverability and reducing bounce rates. On Nagent, NeverBounce is exposed as a fully-configurable email integration that any agent can call — 12 actions, and API key authentication. No code is required to wire NeverBounce into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use NeverBounce to automate the kinds of tasks email teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire NeverBounce into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against NeverBounce, with input parameters and output schema. Drop these into any step of an agent built in Helix.
NEVERBOUNCE_ACCOUNT_INFOTool to get account information including credits, job counts, and usage statistics. Use when retrieving NeverBounce account summary after authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_CONFIRM_POETool to confirm proof of email ownership (POE) from the JavaScript widget. Use when verifying server-side that a user confirmed their email through the widget.
Input parameters
The email address to verify
The verification result status from the widget
Unique identifier for the verification transaction from the widget
Security token from the widget verification
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_JOBS_CREATETool to create a new bulk verification job with parsing, sampling, and callback options. Use for asynchronous list verification with advanced control.
Input parameters
When 'remote_url', a URL to CSV or newline-delimited file. When 'supplied', an array of rows: lists or dicts of primitives.
Display name for the job in the dashboard.
Automatically parse the job after creation (default false).
Automatically start verification after parsing (default false).
Run a free sample analysis instead of the full job (default false).
HTTP/HTTPS URL to receive lifecycle callbacks.
'remote_url' to reference a hosted file; 'supplied' to send inline data.
Custom headers for callback POST requests.
Settings for manual review behavior.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_JOBS_DELETETool to permanently delete a job and its results. Use when you need to irreversibly remove a bulk verification job. This delete is irreversible.
Input parameters
Identifier of the job to permanently delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_JOBS_DOWNLOAD_GETTool to download job results as a CSV file via GET. Use after job completion to retrieve segmented or enriched CSV output. . Options: LINEFEED_0A0D ( ), LINEFEED_0D0A ( ), LINEFEED_0A ( ), LINEFEED_0D ( ) | | `free_email_host` | integer ("0" | "1") | No | Append free_email_host column | | `has_mail_server` | integer ("0" | "1") | No | Append has_mail_server column | | `only_bad_syntax` | integer ("0" | "1") | No | Return only bad-syntax records | | `only_duplicates` | integer ("0" | "1") | No | Return only duplicate entries | | `email_status_int` | integer ("0" | "1") | No | Append email_status_int column | | `include_duplicates` | integer ("0" | "1") | No | Include duplicate entries | | `binary_operators_type` | string ("BIN_1_0" | "BIN_Y_N" | "BIN_y_n" | "BIN_yes_no" | "BIN_Yes_No" | "BIN_true_false") | No | Representation for binary flags. Default is 1/0. Options: BIN_1_0, BIN_Y_N, BIN_y_n, BIN_yes_no, BIN_Yes_No, BIN_true_false | | `mail_server_reachable` | integer ("0" | "1") | No | Append mail_server_reachable column |
Input parameters
Append tld column
Append addr column
Append fqdn column
Append host column
Append alias column
Append domain column
ID of the finished job to download results for
Include valid emails
Append network column
Include invalid emails
Include unknown emails
Include catchall emails
Append subdomain column
Append bad_syntax column
Include disposable emails
Append email_status column
Append has_dns_info column
Append role_account column
CSV linefeed style. Default
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_JOBS_RESULTSTool to retrieve paginated results for a completed job, including original data and verification outcomes. Use after confirming job completion; avoid aggressive polling as repeated calls before completion risk rate limit errors.
Input parameters
Page number to fetch (must be ≥1). Defaults to 1.
The ID of the completed job whose results you want to retrieve.
Number of items per page (1–1000). Defaults to 10.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_JOBS_STARTTool to start a parsed job when auto_start is disabled. Use when you need to manually initiate a job that was created with auto_start=false.
Input parameters
The ID of the job to start. Must reference an existing job created with auto_start disabled.
If true, only a sample of the list will be processed (default: false).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_JOBS_STATUSTool to get the status and progress of a bulk verification job. Use when
Input parameters
The unique identifier of the bulk verification job.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_PARSE_JOBTool to parse a job created with auto_parse disabled. Use when you need to manually parse a job. Cannot reparse once parsed.
Input parameters
The ID of the job to parse. Must reference an existing job created with auto_parse disabled.
Should the job start processing immediately after it's parsed? (default: false)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_SEARCH_JOBSTool to search and list bulk verification jobs in your account with pagination and filtering. Use when retrieving jobs by id, filename, or status, or when listing all jobs with pagination.
Input parameters
The page to grab the jobs from (must be ≥1). Defaults to 1.
Filter jobs based on its id.
Filter jobs based on the filename (exact match).
Filter jobs by the job status (e.g., 'complete', 'running', 'queued').
The number of jobs to display per page (1-1000). Defaults to 10.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_SINGLE_CHECKTool to verify a single email address and gather additional information. Use when you need real-time validation at the point of entry.
Input parameters
Email address to verify
Timeout in milliseconds for the verification attempt. Network latency not included in timeout calculation. Too low a value causes false negatives (premature timeouts reported as unverifiable); too high a value can stall workflows.
Additional request metadata to control verification behavior
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NEVERBOUNCE_WIDGET_SEND_EVENTTool to send widget form events via the JS widget API. Use when reporting form.load or form.completion events after user interactions with your form.
Input parameters
The widget event to send. Supported values: 'form.load' (when the form appears) or 'form.completion' (when the form is successfully submitted).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 64 agents privately built on Nagent that already use NeverBounce.
Build on Nagent
Connect NeverBounce to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find NeverBounce, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, NeverBounce is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once NeverBounce is connected, you configure its 12 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop NeverBounce steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a NeverBounce event fires, the agent kicks off automatically.
Every NeverBounce action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While NeverBounce ships with 12 pre-built email actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching NeverBounce together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build NeverBounce-based workflows tailored to your business.