Admin Reference
Webhooks Route Reference
Understand webhook endpoint management, delivery history, secrets, and the legacy redirect into Connected Systems.
Before you start
- You need outbound event delivery into another system.
Expected outcome
You can manage webhook endpoints safely and understand where the real working desk now lives.
What this route is for
Webhooks is the legacy standalone entrypoint for outbound event delivery, endpoint management, shared-secret rotation, and delivery troubleshooting.
Visibility and route behavior
| Item | Details |
|---|---|
| Route id | webhooks |
| Current behaviour | Redirects into #/connected-systems?section=webhooks. |
| Visibility | Customer-facing when connected-system access is enabled. |
| Direct inbound | Older shell links, bookmarks, search results, and Connected Systems context. |
Main regions, dialogs, and controls
| Surface | What it does |
|---|---|
| Endpoint table | Configured webhook endpoints and event subscriptions. |
| Create dialog | New endpoint with URL, event selection, headers, and active state. |
| Detail dialog | Edit endpoint detail, inspect history, send tests, or regenerate secret. |
| Secret modal | Shows the shared secret after create or regenerate. |
| Delivery history | Delivery status, response code, retries, and retry actions. |
Key actions
- Create a new webhook.
- Choose subscribed events.
- Set custom headers JSON.
- Enable or disable the endpoint.
- Send a test delivery.
- Regenerate the secret.
- Retry failed deliveries.
- Delete the endpoint.
Filters and URL state
| Param | What it controls |
|---|---|
webhookId | Open detail context |
create | Opens create mode |
- Like API Keys, the working desk now sits inside Connected Systems, so the main route state is the destination section plus the active endpoint id.
Outputs and side effects
- Creates or updates live outbound endpoints.
- Sends test deliveries and retry attempts.
- Secret rotation changes what downstream consumers must validate.
Inbound links
- Legacy
#/webhooksbookmarks or shell entrypoints. - Connected Systems
webhookstab.
Outbound links
- Redirect to
#/connected-systems?section=webhooks
Indirect handoffs
- Webhook reliability affects how quickly external systems learn about changes in inspections, defects, quotes, or work orders.
- Event and header configuration here must match the consumer’s expectations or deliveries will continue to fail.
Troubleshooting
| Symptom | What to check |
|---|---|
| Test delivery fails immediately | Re-check endpoint URL, custom headers, and the consumer’s secret validation. |
| The standalone route jumps into another page | That is expected because webhook management now lives inside Connected Systems. |
| Retried deliveries keep failing | Review the recorded status code and any recent secret regeneration or header changes. |