Workflow 1
New-user email validation
Connect this capability to the academy context instead of managing it as a separate operational island.
NB
Available
Email verification integration
Protect email quality with NeverBounce
Use your NeverBounce account to validate addresses in supported AcademyLauncher workflows before messages affect deliverability and sender reputation.
Identify risky or invalid addresses
Protect campaign and transactional delivery
Keep verification usage in your account
Connected workflow
Bring your NeverBounce API key
NB
NeverBounce
Your provider account
AL
AcademyLauncher
Connected academy workflow
Credential
Customer-supplied API key
Billing
Verification usage is billed by NeverBounce
Control
Enable verification where useful
What you can connect
Make NeverBounce part of the learner journey
Use the provider where it creates value while AcademyLauncher keeps the workflow connected to users, products, learning and operations.
Workflow 2
Imported audience verification
Connect this capability to the academy context instead of managing it as a separate operational island.
Workflow 3
Campaign readiness checks
Connect this capability to the academy context instead of managing it as a separate operational island.
Connection process
From provider account to academy workflow
The exact authorization fields vary by provider, but the ownership model remains clear throughout setup.
01
Choose the connection
Select NeverBounce from the AcademyLauncher integration settings for the academy you are configuring.
02
Authorize securely
Complete the bring your neverbounce api key process and provide only the access required for supported workflows.
03
Test the workflow
Confirm the connection before enabling NeverBounce for instructors, learners or live academy operations.
04
Stay in control
Monitor the provider account and rotate, revoke or replace the connection whenever your academy requires it.
Ownership and trust
A connection should remain understandable and reversible
Provider integrations are most useful when your team knows which account is connected, what it enables and how to remove or replace it.
- Customer-supplied API key identifies the connection
- Verification usage is billed by NeverBounce
- Enable verification where useful
- Access should be limited to supported academy workflows
The AcademyLauncher standard
Your connection—not a black box
AcademyLauncher connects the provider to a useful academy experience while preserving a visible path back to the account, credential and permissions behind it.
Read our product principlesRelated connections
Build the rest of the workflow
Connect NeverBounce
Put NeverBounce to work inside your academy.
Bring the provider relationship you control and connect it to a coherent AcademyLauncher workflow.
Identify risky or invalid addresses
Protect campaign and transactional delivery
Keep verification usage in your account