NeverBounce
for LuumenAI
Check email lists against NeverBounce before a send, with bulk jobs held for approval
Connect NeverBounce and Luumen can answer questions about your verification work without you opening the dashboard. Check a single address, look up the status of a running bulk job, page through results, and see how many credits are left. When a new bulk job needs to be created, parsed, started, or deleted, Luumen shows the plan first and waits for your approval.
The NeverBounce toolbox
12 tools: 7 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Account InfoGet account information including credits, job counts, and usage statistics.
- ReadDownload Job Results (GET)Download job results as a CSV file via GET.
- ReadRetrieve Job ResultsRetrieve paginated results for a completed job, including original data and verification outcomes.
- ReadGet bulk job statusGet the status and progress of a bulk verification job.
- ReadSearch bulk verification jobsSearch and list bulk verification jobs in your account with pagination and filtering.
- ReadNeverBounce Single CheckVerify a single email address and gather additional information.
- ReadJS Widget Send EventSend widget form events via the JS widget API.
- WriteConfirm Proof of EmailConfirm proof of email ownership (POE) from the JavaScript widget. Approval by default
- WriteCreate NeverBounce Bulk Verification JobCreate a new bulk verification job with parsing, sampling, and callback options. Approval by default
- WriteDelete NeverBounce JobPermanently delete a job and its results. Approval by default
- WriteStart NeverBounce JobStart a parsed job when auto_start is disabled. Approval by default
- WriteParse NeverBounce JobParse a job created with auto_parse disabled. Approval by default
One prompt, start to finish
What a governed NeverBounce run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — confirm proof of email, create neverbounce bulk verification job, delete neverbounce job, start neverbounce job, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to NeverBounce — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut NeverBounce to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.