Outgoing Webhooks

Outgoing webhooks let Kribana automatically notify your own systems whenever something happens on your account, instead of your tools having to check back with Kribana for changes.

What this does for you

If you run a CRM, a provisioning system, an internal dashboard, or any other tool that needs to know about activity in your Kribana account, you can give Kribana a URL for that tool. Kribana sends it a message when the relevant event happens, so your system can react without manual re-entry.

Each message is cryptographically signed with your account's Key and Secret, so the receiving system can confirm it genuinely came from Kribana and wasn't tampered with in transit.

Who can use it

This is an account-level setting, not something available to individual customers in a self-serve portal.

• Viewing your webhook configuration and credentials requires webhook.view.
• Editing a destination URL or regenerating your security keys requires webhook.edit.
• This feature must also be enabled for your account — if you don't see a "Webhooks" option, ask your Kribana contact to confirm it's turned on.

Where to find it

In your account settings, go to Webhooks, organized into Credentials and Endpoints groups.

How to use it

1. Under Credentials, the Authorization panel shows a Key and a Secret — use the copy icon to grab either value and the reveal toggle to view them (hidden by default).
2. Under Endpoints, you'll see Incoming Webhooks (a read-only reference showing the URL your account receives webhook calls on) and Outgoing Webhooks — the one you configure, listing each destination Kribana can notify.
3. To set or change a destination, click Edit on its row in Outgoing Webhooks, enter the full URL your receiving system listens on (starting with http:// or https://), and click Save, or Cancel to discard.
4. If you need to invalidate your existing keys — for example, if you suspect they've been exposed — click Regenerate keys and confirm ("Yes, regenerate"). Your old keys stop working once you do this.

Tips / things to know

• Regenerating your keys invalidates every existing webhook connection on your account, not just one destination — update any system that verifies incoming Kribana messages with the new Secret at the same time, or it will start rejecting messages.
• Leave a destination's URL blank if you don't want that notification sent.
• The exact set of destination rows and what event each represents is configured for your account — check the label on each row rather than assuming a fixed list.
• There's no history or log visible in the product showing past deliveries or whether a notification succeeded — check your receiving system's own logs if a message seems missing.
• You can edit the URL for destinations already listed on your account, but there's no button to add a brand-new destination yourself — reach out to your Kribana contact for that.
• There's no "send a test notification" button, and no visibility into delivery history from within the product.
• The exact payload shape for each event isn't documented in the product interface — check with your Kribana contact if you need the schema to build against.