Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the JumpCloud connector page.Copy your Native Webhook URL
Before configuring JumpCloud, copy the Native Webhook URL from this connection in StackOne Hub. This is the address JumpCloud will POST events to. You will paste it into the URL field when you create the webhook channel in the next steps.
Create a webhook channel in JumpCloud
Sign in to JumpCloud and add a webhook channel that points at StackOne.
Sign in to JumpCloud
Sign in to the JumpCloud Admin Portal with an administrator account.
Open Settings and Notification Channels
In the left navigation, open Settings, select the Notification Channels tab, then select the Webhook tab and click Add.
Enter the name and Native Webhook URL
On the Create Webhook screen, enter a Name for the channel (for example, StackOne Integration), and paste the Native Webhook URL you copied from StackOne Hub into the URL field. Leave Content-Type set to application/json, keep Verify SSL Certificate enabled, and click Create.
Send events to the channel with an Insights Rule
A webhook channel only receives the events that an Insights Rule sends to it.
Create an Insights Rule
Create an Insights Rule that matches the directory events you want to receive (for example user lockouts, user creation, or authentications), and select the webhook channel you just created as the rule’s notification channel. JumpCloud will then POST an alert to the Native Webhook URL each time the rule matches.
Available webhook events
JumpCloud delivers webhooks through Directory Insights Rules rather than a fixed set of named events, so the connector exposes a single generic event. Which directory events it fires on is determined entirely by the Insights Rules you attach to the channel.
Directory Insights events
Fired by any Insights Rule attached to the webhook channel.
- Directory Insights Alert (
insights_alert) — Fired when an Insights Rule matches a directory event (for example a user lockout, user creation, or authentication). The underlying event is identified by the payload’stypefield.
Delivery format
Details of how JumpCloud delivers events to StackOne.
Review the payload format
JumpCloud sends a single JSON object per alert (not a batched array). The payload’s type field names the underlying event (for example user_lockout), a tags array carries the event’s key/value details, and organization_object_id identifies your JumpCloud organization. JumpCloud does not sign webhook deliveries, so the unguessable Native Webhook URL is what keeps the endpoint secure.