Juvaro Help Centre
Dansk

Webhook triggers

Let an outside system start a run by calling a URL, and rotate or disable the secret.

Who can do thisWorkspace Administrator

A webhook trigger is a third way to start a run, next to the schedule and Run now. An outside system calls a URL, and the Hub runs the connection. Use it when the source system knows best when there is new data, for example after an export finishes.

Note

The Integration Hub is in English only, so its labels are quoted in English in the Danish articles too.

Which connections can have one

  • Microsoft Intune, Jamf Pro and Generic REST / JSON connections can.
  • Shared mailboxes cannot. They are checked on their schedule.
  • The Webmercs vendor connection cannot. Flexshop sends it orders directly.
  • The platform rows that Juvaro runs cannot. Trying gives a message that ends "so it cannot be given a webhook here."

Turn on a webhook trigger

You find the card Webhook trigger at the bottom of the connection's page. The same section is at the end of the connection's editor, but only once the connection has been saved; before that it says "Save the connection first, then a webhook URL + secret appear here."

  1. Open the connection's page from Connections.
  2. In Webhook trigger, click Enable webhook trigger.
  3. Two fields appear: Webhook URL and Secret (copy now - shown once). Click in a field to select its value.
  4. Copy both into the system that should start the runs. That system sends the secret as a bearer token in the Authorization header when it calls the URL.
Note

The secret is shown only this once. When you leave the page, the card shows just the last four characters, for example "Secret set (…7f3a). Rotate to get a new one." If you did not copy it, rotate it to get a new one.

The Webhook URL is the same for every connection in the Hub. The secret is what tells the Hub which connection to run, so treat it like a password. If the card says "Not configured yet." in place of the URL, the Hub's webhook address has not been set up for your environment; contact Juvaro support.

Rotate the secret

Rotate the secret when someone who knew it leaves, when it may have leaked, or as routine.

  1. Click Rotate secret in the Webhook trigger card.
  2. Copy the new secret from Secret (copy now - shown once).
  3. Update the calling system with the new secret.

The card then shows "Last rotated" with the time. The new secret replaces the old one, so the calling system must be updated before its next call.

Turn it off

Click Disable. Calls to the URL no longer start this connection. If you click Enable webhook trigger again later, you get a brand new secret, and the calling system needs it.

See the deliveries

While the trigger is on, the card shows the runs that a webhook started, as a run history named after the connection with "webhook deliveries" added. In the main Run history the same runs show Webhook in the Trigger column.

The card also says: "Accepted deliveries only - rejected or rate-limited attempts are not recorded." A call with a wrong secret, or one that is refused because it came too often, leaves no trace in the Hub. If you expect a run and see none, check the calling system's own log first.

Good to know