Find out who changed a webhook
Do this when a webhook stops sending and you find it disabled, pointed somewhere new, or sending fewer events than before, and you need to know who did it and when. Each change to an endpoint adds a row to Audit: creating, editing, rotating its secret, sending a test, redelivering and deleting. An edit records what the endpoint looked like after it and which settings changed.
Who can do this: requires the org admin role (Org Owner or Org Admin). Your plan must include both webhooks and Audit. Without Audit, opening it shows Not on your plan.
- In the sidebar, select Audit. It opens on the Activity tab, newest action first, showing Changes.
- In the Search or filter activity box, type the name of the webhook and press Enter, or select Search for with your text. The search shows as a chip, and the list keeps only actions whose text matches. To see every webhook action, search for webhook instead.
- Narrow the time with From and To if you know roughly when it broke. Times are in your time zone; hover From or To to see which one.
- Read down the list. Each row says what was done, who did it and how long ago:
- Created webhook and the name, when it was set up.
- Updated webhook, for any edit to its name, URL, events, projects or Enabled.
- Rotated the secret of webhook, when someone selected Rotate.
- Sent a test ping to webhook and Redelivered to webhook, for Send test and Redeliver.
- Deleted webhook, when it was removed.
- Select an Updated webhook row, or Details in its ⋯ menu. The action opens beside the list. The Event tab names the Actor who made the change and When.
- Select the Payload tab. changed lists the settings the edit touched, such as
enabledorevent_types, and the rows under it show their values after the edit. The URL shows only as the host it points to, never the full address, since a receiver's address can hold its own key. To see the value before the edit, open the previous change to the same webhook. - To share what you found, copy the page's address: each action has its own link, and the search and dates are kept in it.
Then put the endpoint right on its Settings tab, as in Change which events a webhook sends, and check it with Send test. A delivery that failed while it was wrong can be sent again with Redeliver, as in Fix a failing webhook. Events that happened while it was disabled were never sent, so there is nothing to redeliver for them.
Related
- Find an event in the audit log: every way to search and filter Activity.
- Audit: each column and tab in Activity and an event's details.
- How webhooks work: endpoints, events and what Enabled does.