Workflow 1
Transactional academy email
Connect this capability to the academy context instead of managing it as a separate operational island.
EA
Flexible connection
Email and messaging integration
Connect an approved email API to academy communication
Use configurable email-provider credentials where supported so your academy can keep its sending identity and provider relationship.
Use an approved provider account
Keep sender identity under your control
Connect delivery to academy notifications
Connected workflow
Configure your email provider
EA
Custom Email API
Your provider account
AL
AcademyLauncher
Connected academy workflow
Credential
Provider API or SMTP credentials
Billing
Provider plan remains yours
Control
Replace credentials when needed
What you can connect
Make Custom Email API 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
Learner notifications
Connect this capability to the academy context instead of managing it as a separate operational island.
Workflow 3
Operational communication
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 Custom Email API from the AcademyLauncher integration settings for the academy you are configuring.
02
Authorize securely
Complete the configure your email provider process and provide only the access required for supported workflows.
03
Test the workflow
Confirm the connection before enabling Custom Email API 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.
- Provider API or SMTP credentials identifies the connection
- Provider plan remains yours
- Replace credentials when needed
- 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 Custom Email API
Put Custom Email API to work inside your academy.
Bring the provider relationship you control and connect it to a coherent AcademyLauncher workflow.
Use an approved provider account
Keep sender identity under your control
Connect delivery to academy notifications