Webhooks¶
Send an HTTP request to your own systems when something happens in Adverity Atlas, an automation finishing, an artifact being published, so you can react without polling. Found at Settings > Integrations > Webhooks.
Prerequisites¶
Admin role at the tenant level.
An HTTPS endpoint that can receive POST requests.
Creating a webhook¶
Go to Settings > Webhooks and click Add Webhook. A panel opens, titled Add Webhook, for subscribing to platform events.
Fill in the form and click Create Webhook. The subscription appears in the table and delivery starts immediately.
Field |
What it does |
|
|---|---|---|
Display Name |
How the subscription is labelled in the table |
Required |
Target Url |
The endpoint that receives the POST |
Required |
Secret |
Used to HMAC-sign each request so you can verify it came from Adverity Atlas. Pre-filled with a generated value, minimum 16 characters |
Required |
Event Patterns |
Exact event names or wildcards, so |
Optional |
Workspace Id |
Scope to a single workspace, so it fires only for activity there. Leave unset for the whole tenant |
Optional |
Max Consecutive Failures |
How many failures in a row before the subscription is disabled automatically. Defaults to 10 |
Optional |
Warning
The secret is what proves a request came from Adverity Atlas. Store it wherever your receiving service verifies signatures, and treat it like any other credential.
Editing an existing subscription adds one more control: switch it inactive to pause delivery without deleting it.
Delivery and failure handling¶
The table shows each subscription’s health: its Status, how many Failures it has accrued in a row, and when it Last Delivered. The Deliveries action opens a Delivery History panel listing that subscription’s recent delivery attempts.
Adverity Atlas does not store the body of each delivery, only the outcome of the attempt.
Delivery is resilient by design:
Automatic retries: A failed delivery is retried automatically with exponential backoff, up to five attempts
Auto-disable: Consecutive failures are counted. After a threshold of repeated failures (10 by default), the webhook is disabled automatically so a dead endpoint does not accrue an unbounded backlog
Re-enable: A disabled webhook records the reason, and can be re-enabled once the endpoint is fixed
Tip
Point a new webhook at a request-inspection endpoint first to see the real payload shape before wiring it into your own systems.
Permissions¶
Tenant Admin only.
What’s next?¶
Automations, a common source of the events you subscribe to
Audit logs, the in-product record, alongside outbound webhooks