Subscribe to Help Center RSS FeedWith JumpCloud's Webhook Notification Channels, you can add specific URLs to define who you want to notify regarding critical alerts and and their related events. This is a list of frequently asked asked questions related to Webhook Channels.
Webhooks allow you to receive real-time notifications when specific events occur in JumpCloud, such as alerts and selected DI events. They help integrate JumpCloud with external systems like SIEMs, ticketing tools, or automation platforms.
Webhooks can be triggered by:
- Alert notifications (e.g., low disk space, unauthorized software, etc.)
- Directory Insights events
- Access Management events
JumpCloud webhooks use the POST method to send event data in JSON format to the configured URL.
While setting up the channel, you can:
- Mask sensitive header values using the “Sensitive Value” toggle.
- Protect tokens in the webhook URL (e.g., https://api.example.com/hook/{{TOKEN}}) — these values are encrypted and not retrievable after saving.
See Create Webhook Channel to learn more.
Yes. You can configure multiple static headers per webhook channel. Some can be marked as sensitive (like API keys).
JumpCloud retries webhook delivery three times with exponential backoff for HTTP status codes 5xx, 408, or 429.
After configuring a webhook channel, you can send a test event from the UI to validate connectivity.
At this time, payloads follow a fixed JSON schema per event type. Future enhancements may support custom field mapping or transformations.
Failures are logged in the Directory Insights.
Yes. Webhook channels are reusable and can be linked to multiple alert rules or other services within the platform.
In this Article
Learn More