Integrations and automation
Connect Inbox Academy to Zapier
Last updated
Zapier connects Inbox Academy to thousands of other tools. The useful part is simple: when something happens somewhere else — a deal closes in your CRM, a contract is signed, a new starter appears in your HR system — that person is enrolled in a course without anyone remembering to do it.
No code is involved. You pick the event in one tool and the course in ours.
What you need first
A Zapier account.
An API key for your organization. Only admins can create one - see Create and revoke an API key.
The slug of the course you want people enrolled in. You can find it on the course page; it is the short label in the course's web address.
Setting it up
Open the Inbox Academy app on Zapier and start a new Zap.
Choose the trigger - the event in your other tool that should enroll someone. "New deal won" or "New employee added", for example.
Add Inbox Academy as the action, and connect your account by pasting your API key when asked.
Map the learner's email address from the trigger, and enter the course slug.
Choose whether to skip verification - see below.
Test it, then turn the Zap on.
Name the API key "Zapier" when you create it. If you ever disconnect the Zap, you will know exactly which key to revoke.
Testing a Zap enrolls a real person
Zapier's test step sends a real request, so it creates a real enrollment, and your free trial starts the moment your first learner enrolls.
If you are still on a trial you have not started, build the course first, then test with your own address when you are ready for the clock to start.
Skip verification
This decides whether the learner has to confirm their email address before the course begins.
Skip verification | What happens |
|---|---|
Yes | The course starts straight away, and the first lesson goes out on its own schedule — the same as a learner you add yourself. |
No | The learner is sent a confirmation email, and nothing else arrives until they follow the link in it. |
Skip it when the trigger already proves the person expects the course, a customer who just signed, a colleague who just started. Keep verification when it does not, such as a form on a site you do not control, where anyone could type in anyone's address.
Skipping verification means you are vouching for the address
A course arriving unasked is spam to the person receiving it, however good it is, and enough of those damages delivery for all of your learners. If you are not sure the person asked for it, let them confirm.
If you built your Zap before this option existed, it will not appear until you update the Inbox Academy step to the latest version of the app. Until then, those Zaps enroll people without a confirmation email.
What happens when it goes wrong
If Zapier reports | It usually means |
|---|---|
The key was rejected | The API key was revoked, or pasted incompletely. Create a new one and reconnect. |
Course not found | The slug does not match a course in this organization. Slugs never change, so check for a typo. |
No room for new learners | Your organization has reached the learner limit on your plan. |
Nothing, but no enrollment appears | The learner was already enrolled. Enrolling someone twice does nothing, and that is not an error. |
Because a course slug can never change, a Zap keeps working however much you edit the course behind it — rename it, rewrite every lesson, reorder the content.