Webhooks

Choose a channel

Outbound learning data is configured once, in Users → Manager Notifications. Webhook is the real-time channel. The same screen can also email a person or drop a nightly file.

Most webhooks fire as the learner acts. Two exceptions: subscription purchases (bundlePurchase) wait about an hour for financial systems; inactivity webhooks send daily at noon. Course-view reports are SFTP only.

Common jobs

Start with one trigger. You can add more notifications later — each one is a trigger + a channel + a destination.

Set it up

You need a public URL that accepts POST. That can be your own HTTPS endpoint, or a no-code catch URL such as a Zapier Catch Hook. Then, in Admin:

1. Go to Users → Manager Notifications (/learn/manager/notification).
2. Click Add Notification.
3. Choose the trigger from the “When a …” list (for example, “course is completed by a learner”).
4. Select Webhook. Almost every trigger offers it; course-view reports do not.
5. Paste the destination URL. The form example is https://www.example.org/path.
6. Optionally limit the notification to one course or learning path. The default is every item on the site.
7. Click Test Event. When the sample arrives, click Save Notification.

Screenshots of this path are in Configuring Webhook Data Transfers and Setting Up Automated Data Notifications. Learner Notifications and System Notifications on the same Users menu are different features (campaigns and default learner emails).

Get a sample before you write mapping code

Field sets differ by trigger. Do not invent an envelope. On the same Add Notification form:

• Download Sample JSON (or CSV) for the selected trigger. If the sample is empty, perform that action in the site once — it can take up to two hours to appear.
• Test Event POSTs a representative sample to the URL you entered. Use that to confirm headers, body shape, and that your endpoint is reachable.

The posted body is the same event record as GET /incoming/v2/events/:kind. Realtime delivery wraps the object in a JSON array. Learner email is user; profile fields (name, externalCustomerId, custom refs) are on userDetail; the course or path UUID is notifiableId. IDs are UUIDs.

[
  {
    "event": "courseCompletion",
    "timestamp": "2026-03-13T16:45:00.000Z",
    "companyId": "11111111-1111-1111-1111-111111111111",
    "notifiableId": "22222222-2222-2222-2222-222222222222",
    "title": "API Fundamentals",
    "user": "[email protected]",
    "userDetail": {
      "id": "33333333-3333-3333-3333-333333333333",
      "firstName": "Jane",
      "lastName": "Doe",
      "externalCustomerId": "cust-100"
    }
  }
]

Extra keys from the underlying course-action row are present on a live event. Trust Test Event / Download Sample JSON over this sketch.

Receive the POST

Each firing is its own request. Return a status in 200–308 within 15 seconds or the attempt fails. Failed deliveries retry 10 times with backoff from 20 seconds up to 3600 seconds (about 3.5 hours). There is no delivery log in Admin — watch your own endpoint.

// Acknowledge first — the worker times out at 15 seconds.
app.post('/webhooks/ti', (req, res) => {
  res.status(200).end();

  const items = Array.isArray(req.body) ? req.body : [req.body];
  for (const item of items) {
    // item.event is the trigger kind, e.g. "courseCompletion"
    // item.user is the learner email
    // item.notifiableId is the course (or path) UUID
    console.log(item.event, item.user, item.notifiableId);
  }
});

Logins and visits

Both webhooks include userDetail.role, so you can segment managers from learners in an automation.

User Logs In fires for managers and learners. User Visits Site fires only when a learner visits.

All webhook triggers

The label is what you pick in Admin. The kind is the event field on the JSON, and the path segment on GET /incoming/v2/events/:kind.

SFTP and polling