Guide to Thought Industries Webhooks: Features and Best Practices
Thought Industries is a learning platform for customer, partner and professional education. Its webhooks report what learners do, such as enrolling, completing a course, passing a quiz or buying access, so you can update a CRM, issue a credential or start a billing workflow.
This guide covers how Thought Industries webhooks work as Manager Notifications, the trigger list and payload fields, verifying X-Ti-Hook-Signature with a secret you request from Support, and a short retry window with no delivery log.
What are Thought Industries webhooks?
Thought Industries delivers webhooks through Manager Notifications. Each notification pairs one trigger, such as "course is completed by a learner", with a channel. When you choose the Webhook channel, the notification posts each event as a single JSON object to the URL you enter. To receive several triggers, you add several notifications, which can share one URL.
Notifications are configured only in Admin, not through the REST API. A notification can cover every course on the site or be limited to one course or learning path.
Thought Industries webhook features
| Feature | Details |
|---|---|
| Signature | hex HMAC-SHA256 |
| Signature header | x-ti-hook-signature |
| Body | JSON |
| Event routing | Body field event |
From the Thought Industries webhooks page:
- Each request carries one event. The body is the same record that
GET /incoming/v2/events/:kindreturns from the Events API. - Any status from
200to308counts as success, but a response slower than 8 seconds can fail the attempt. - A failed delivery is retried twice, about 1 minute and then about 2 minutes later. After the third failure the event is dropped.
- There's no delivery log in Admin.
- Most events are sent as they happen.
bundlePurchase(used for subscriptions) waits about an hour, and the inactivity triggers send daily at 12:00 in the instance timezone.
Events and payloads
Route on the top-level event, which holds the trigger kind. Thought Industries lists 31 kinds. Some of the course triggers:
| Event routing | Body field event |
The full list also has learning path triggers (learningPathEnrollment, learningPathAction), learner triggers such as login, visit, registration, award and redemptionCodeRedeem, the inactivity triggers userLastActive7, userLastActive14 and userLastActive31, and commerce triggers including productPurchase, bundlePurchase, subscriptionCancel and subscriptionReactivation. login fires for managers as well as learners, while visit fires only for learners. Both include userDetail.role.
Field sets differ by trigger. Thought Industries shows only a sketch of the fields every courseCompletion event has, and says a live event adds keys from the underlying record:
{
"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": "jane@example.com",
"userDetail": {
"id": "33333333-3333-3333-3333-333333333333",
"firstName": "Jane",
"lastName": "Doe",
"externalCustomerId": "cust-100"
}
}
user is the learner's email, userDetail the profile, and notifiableId the course or learning path UUID. For a real sample of any trigger, use Download Sample JSON on the notification form or Test Event.
Setting up Thought Industries webhooks
- In Admin, go to Users > Manager Notifications and click Add Notification.
- Choose the trigger from the "When a ..." list.
- Select Webhook and paste your URL, for example
https://example.com/webhooks/thought-industries. - Optionally limit the notification to one course or learning path.
- Click Test Event, check the sample arrived, then click Save Notification.
- Ask Thought Industries Support for your Site Secret and store it as
TI_SITE_SECRET. It isn't your API key and isn't shown in Admin.
Ask Thought Industries Support for your Site Secret and use it as the verification secret.
To route through Hookdeck, create a Thought Industries source with the Site Secret and use its URL in each notification. For local development:
npx hookdeck-cli listen 3000 thought-industries --path /webhooks/thought-industries
Securing Thought Industries webhooks
Every request, including Test Event, carries X-Ti-Hook-Signature: sha256= followed by the lowercase hex HMAC-SHA256 of the raw body, keyed with the Site Secret. The secret doesn't rotate on its own. Support rotates it when you ask.
Node.js verification
const crypto = require('node:crypto');
function verifySignature(rawBody, headers, secret) {
if (!Buffer.isBuffer(rawBody) || typeof secret !== 'string' || !secret) return false;
const signature = headers['x-ti-hook-signature'];
if (typeof signature !== 'string') return false;
const key = Buffer.from(secret, 'utf8');
const message = rawBody;
const candidates = [signature.startsWith('sha256=') ? signature.slice(7) : signature];
const expected = crypto.createHmac('sha256', key).update(message).digest();
return candidates.some((candidate) => {
if (!/^[0-9a-fA-F]{64}$/.test(candidate)) return false;
const received = Buffer.from(candidate, 'hex');
return received.length === expected.length && crypto.timingSafeEqual(received, expected);
});
}
The handler builds a deduplication key, as Thought Industries suggests: id when the event has one, otherwise event, user, notifiableId and timestamp together.
const express = require('express');
const app = express();
app.post('/webhooks/thought-industries', express.raw({ type: '*/*' }), async (req, res) => {
const secret = process.env.TI_SITE_SECRET;
if (!secret) return res.sendStatus(500);
if (!verifySignature(req.body, req.headers, secret)) return res.sendStatus(401);
let item;
try {
item = JSON.parse(req.body.toString('utf8'));
} catch {
return res.sendStatus(400);
}
if (!item || typeof item !== 'object' || Array.isArray(item)) return res.sendStatus(400);
if (typeof item.event !== 'string') return res.sendStatus(400);
const key =
typeof item.id === 'string'
? item.id
: [item.event, item.user, item.notifiableId, item.timestamp].map(String).join('|');
try {
if (await alreadyHandled(key)) return res.sendStatus(200);
await queue.add('ti-event', { key, kind: item.event, courseId: item.notifiableId, item });
await markHandled(key);
} catch {
return res.sendStatus(503);
}
res.sendStatus(200);
});
queue, alreadyHandled and markHandled stand for your own job queue and deduplication store.
Hookdeck's Thought Industries source type runs the same check. It returns 200 and records any mismatch as failed verification. Hookdeck doesn't add a freshness window, and Thought Industries's signature has no timestamp to check against.
Make Thought Industries webhooks production-ready. Hookdeck Event Gateway logs every delivery, which Thought Industries Admin doesn't, and keeps retrying your service long after Thought Industries' three attempts would have dropped the event.
Thought Industries webhook limitations and pain points
Events are dropped after three attempts
The Problem: A short outage on your endpoint loses enrolments, completions or purchases.
Why It Happens: Thought Industries makes 3 attempts within a few minutes, then drops the event.
Workarounds:
- Backfill gaps from the Events API with
GET /incoming/v2/events/:kind. - Alert on endpoint errors so you know when to backfill.
How Hookdeck Can Help: Hookdeck accepts each delivery, stores it, and retries your service on your schedule, with replay for anything that failed.
No delivery log in Admin
The Problem: You can't see in Thought Industries what was sent or whether it succeeded.
Why It Happens: The webhooks page says Admin has no delivery log and recommends logging on your own endpoint.
Workarounds:
- Log the event kind, key and response status for every request, without learner details.
- Compare counts with the Events API periodically.
How Hookdeck Can Help: Hookdeck records every request with headers, body and delivery attempts.
The Site Secret comes from Support
The Problem: You can't set up verification, or rotate the secret, from Admin.
Why It Happens: The Site Secret isn't displayed in Admin. Support issues it and rotates it on request.
Workarounds:
- Request the secret early, before you need to go live.
- Plan a rotation with Support so you can switch the stored value at the same time.
How Hookdeck Can Help: With Hookdeck verifying, the secret lives in one place, and your own services don't need it.
One trigger per notification and loose payloads
The Problem: Covering many triggers means many notifications, and each trigger has its own field set.
Why It Happens: Each Manager Notification has one trigger, and the docs publish only a sketch of shared fields.
Workarounds:
- Point all notifications at one URL and route on
event. - Download a sample for each trigger you use before writing mapping code.
How Hookdeck Can Help: Hookdeck filters can route each event kind to the service that handles it.
Best practices
Answer within 8 seconds
Queue the event and respond, then sync to your CRM or billing system in a worker. See processing webhooks asynchronously.
Deduplicate on a composite key
Retries can send an event again. Use id where present, otherwise event, user, notifiableId and timestamp, as in the idempotency guide.
Separate managers from learners
login fires for both. Check userDetail.role before counting a login as learner activity.
Expect delays on some triggers
Don't treat a missing bundlePurchase as a failure until an hour has passed, and expect inactivity triggers once a day.
Conclusion
Thought Industries webhooks are Manager Notifications that post one event per request, signed with sha256= plus a hex HMAC-SHA256 keyed with a Site Secret from Support. Respond within 8 seconds, deduplicate on a composite key, and backfill from the Events API, since failed events are dropped after three attempts and Admin keeps no log.
Hookdeck Event Gateway verifies Thought Industries requests, logs them and retries delivery to your services.
Get started with Hookdeck for free and handle Thought Industries webhooks reliably in minutes.