Webhooks
Jimo provides webhook integrations to allow real-time event tracking and automation. This reference guide details all available webhook events that can be configured and consumed by external apps.
Last updated
Was this helpful?
Jimo provides webhook integrations to allow real-time event tracking and automation. This reference guide details all available webhook events that can be configured and consumed by external apps.
Last updated
Was this helpful?
Webhooks enable you to receive notifications when specific actions occur within Jimo, such as experience interactions, content updates, or user events.
These webhooks can be used to synchronize Jimo with your internal systems, CRMs, or analytics platforms.
Webhook events are grouped into the following categories:
Tours: Events related to tour creation, updates, and user interactions.
Surveys: Events for survey creation, responses, and status changes.
Checklists: Events tracking checklist actions and progress.
Hints: Events for hint interactions and modifications.
Banners: Events monitoring banner changes and user views.
Changelog Posts: Events for changelog content updates.
The list of events is documented on the link bellow
Each webhook event follows a standardized JSON payload structure containing key information about the triggered action. The general format is as follows:
Below is an payload example for a tour.completed
event:
To create, update, or delete webhooks, navigate to Settings > Integrations > Webhooks in Jimo. You can:
Add new webhooks by specifying an endpoint and selecting events.
View and edit existing webhooks.
Monitor webhook activity, including success and failure logs.
If a webhook request fails (e.g., due to your endpoint being down), Jimo automatically retries sending the event at several intervals. Ensure your endpoint is capable of handling retries and logging errors for troubleshooting.
We consider that a webhook request failed if the status code returned by your endpoint is 400
or above.
Our retry schedule is approximately as follow :
1 hour after first failure
3 hours later
1 day later
3 days later
1 week later
You can also launch a manual retry from the webhook activity monitoring page.
For a step-by-step guide, visit our