V1 and V2, side by side
Everything so far has changed how your school looks. Webhooks are about what it does: telling your other tools, the moment something happens, so they can act on it without anyone copying and pasting.
A message, sent when something happens
A webhook is Teachable sending a short message to an address you choose, automatically, whenever a particular thing happens. A student enrols, and a message goes out. A payment is refunded, and another one goes out.
The address belongs to something you control: a spreadsheet script, an automation tool, a small program on a server. It reads the message and does whatever you've told it to: add a row, send an email, update your CRM.
Webhooks and the API are opposites
| Webhook | API | |
|---|---|---|
| Who starts it | Teachable, when something happens | You, when you want to know something |
| Good for | Reacting straight away | Looking things up, catching up, changing things |
| Analogy | A text message arriving | Picking up the phone to ask |
Most real integrations use both: webhooks to react, and the API to fill in details and check nothing was missed. The last section of this course covers the API.
Where they live
- In your admin, go to Settings › Webhooks and click Add Webhook.
- Choose the event, such as a new enrolment, and paste in the address to send it to.
- Webhooks need the Growth plan or above.
Each webhook shows a status, Pending until it has sent its first message, Active once it's working, and Inactive if it keeps failing or you cancel it. There's a history, too, listing every message it sent.
Three webhooks sounds limiting. The trick is to send them all to one address that you control, and let that one place decide what to do with each kind of event. The Automation without Zapier lesson shows how.
In short
- A webhook is Teachable sending a message to your address when something happens.
- Webhooks react; the API asks. Good integrations use both.
- Set them up in Settings › Webhooks, on the Growth plan or above.