The job of this console
Subscribe an endpoint, verify signatures on the partner side, watch deliveries, and retry a failed batch. Pause or delete a subscription that is flooding a dead URL.
Admin · Extensibility
Webhooks
Subscribe to domain events, inspect deliveries, and retry failures.
Scroll to Flowcharts. Scenario: Subscribe to a domain webhook.
Outbound events
Subscribe, inspect deliveries, retry a miss
Webhooks subscribe to domain events, show delivery attempts, and retry failures. They push what already happened on Employee, leave, ticket, and similar records.
Admin → Developer portal → Webhooks
Route
/admin/webhooks
Org flag webhooksEnabled
HR Admin · Org Admin · integration owner
Seat at the table
Integration owners with Admin access. Endpoint servers are outside Tracopus; this console only manages the subscription.
The working rhythm
Add a subscription, send a test if offered, watch the delivery log, retry failures, disable when the partner is down for a long window.
Moments that bring you here
Go-live of a connector. A spike of 4xx/5xx. After rotating an endpoint URL. When automation also notifies and you must avoid double fire.
ⓘ
Webhooks are not the system of record
A missed delivery does not mean the leave or ticket vanished. Retry the push; do not recreate the source row.
Flowcharts
1 — Create a subscription
Add an HTTPS endpoint, pick events, then watch the delivery log.
flowchart TD
A[Open Webhooks] --> B[Create subscription]
B --> C[HTTPS endpoint + events]
C --> D[Save]
D --> E[Inspect deliveries]
E --> F[Retry failures]
- 1Open WebhooksDeveloper hub → Webhooks.
- 2CreateHTTPS URL, secret, event types.
- 3DeliveriesSuccess vs retry vs dead-letter.
- 4Fix endpointThen retry — do not duplicate subscriptions.
Overview
Webhooks fan out existing domain events. Payloads must stay masked for sensitive fields.
How to use
1. HTTPS only
Reject cleartext endpoints.
2. Verify signatures
Integrators must check the signing secret.
3. Idempotent receivers
Retries are expected.