Webhooks and deliveries

Before you begin

• Feature/capability and own HTTPS receiver.

Step by step

1. 01

   Open Administration → Webhooks in the correct department. In New webhook enter name, HTTPS endpoint and events, one per line; ticket.* selects ticket events and * selects all events. HTTP endpoints do not enable creation; loopback and special-use destinations are rejected.

2. 02

   Create the subscription and transfer the one-time secret to the authorised receiver through the intended channel. Close the panel after storing it; keep it out of screenshots, tickets and support chats.

3. 03

   Edit name, endpoint or events and use Active subscription/Save webhook to pause or reactivate it. Check Paused before maintaining the receiver.

4. 04

   In Recent deliveries filter by subscription; zero deliveries means there are no outcomes to inspect. Only with your own HTTPS receiver ready, produce a synthetic event and verify HMAC/CloudEvents, HTTP result and attempts.

5. 05

   Inspect failures before replay, available for dead-letter deliveries. Coordinate secret rotation with the receiver, then verify a new delivery.

The result to check

Persistent independent deliveries per destination.

Limits and considerations

• Disallowed destinations are rejected. A successful delivery does not prove that the receiving system processed the event. Use only destinations you are authorised to configure and check.
• Enabling Webhooks does not configure the HTTPS receiver. Prepare the receiver and use an authorised test event to check the HMAC signature, CloudEvents format, HTTP response and recorded attempts. With no deliveries, there are no outcomes to inspect.

Continue with related guides