How to create and manage webhooks that send Continu event data to third-party systems — for Assignment, Content, Badge, and Workshop events.
Webhooks send Continu event data as JSON to a third-party URL whenever specific events happen. Supported events: Assignment Completion, Content Completion, Badges Awarded, Workshop Attendance.
Use webhooks to push Continu data into systems that aren't natively integrated — analytics platforms, custom dashboards, automation tools.
How to Create a Webhook
Step One: Navigate to Admin > Developer Tools from the left-hand navigation.
Step Two: Select the Webhooks option, then click Add A Webhook in the top right.
Step Three: Fill in the webhook information:
Name — descriptive name for the webhook (used for admin reference).
URL — the endpoint the webhook will deliver to.
Event Types — toggle which event types trigger the webhook. Select one, some, or all.
Click Save when fields are populated.
Step Four: Validate and activate the webhook. Once saved, the webhook can be validated against the target URL. After validation succeeds, click Activate.
Managing Existing Webhooks
Logs. Click the webhook's name to view the log of records sent. Logs can be downloaded as CSV from the download button at the top right.
Activate / Deactivate. Use the three-dot menu next to a webhook to activate or deactivate it. Deactivated webhooks don't fire but remain configured for future use.
Edit. The three-dot menu also opens the edit page where you can change Name, URL, and Event Types. Validations can be re-run from here.
Archive. Webhooks you no longer use can be archived. Archived webhooks move to the Archived section and can be restored later.
Configuration Pitfalls
Activating Without Validating. An activated but unvalidated webhook may fail silently. Validate against the target endpoint first.
Target URL Not Returning 2xx. The receiving endpoint should return a 2xx HTTP status code for Continu to consider the delivery successful. Non-2xx responses are logged but may not retry depending on configuration.
Selecting All Event Types Without a Reason. A webhook firing on every event creates significant volume. Select only the event types the receiving system actually consumes.
Logs Filling Up. Webhook logs accumulate over time. Download and clear logs periodically if storage on the Continu side is a concern.
Endpoint Changes Without Updating the Webhook URL. If the receiving system's URL changes, webhook deliveries fail until the URL is updated in Continu.
See Also
- Provisioning and Sync: How User Data Flows Into Continu — broader data flow context.
- Notifications: Architecture and Strategy — for in-Continu notifications (vs webhook-based external notifications).