Webhooks

Push Events to Any System in Real Time

Webhook delivery with HMAC signatures and automatic retries. Connect Slack, email, PagerDuty, or any system that accepts HTTP callbacks.

HMAC signaturesAutomatic retriesDelivery logs
Webhook Configuration

Why Polling Doesn't Cut It

Real-time events need push delivery, not constant checking.

Polling for Updates

Hitting an API every few seconds to check for changes wastes resources and still leaves you seconds behind. Real-time events need push, not pull.

Manual Notification Setup

Building a custom integration for every alert channel - Slack, email, PagerDuty - is weeks of work. And maintaining it is a recurring headache.

Disconnected Systems

Monitoring data in one place, ticketing in another, billing in a third. Without real-time connections, you're copy-pasting between systems.

Webhooks That Just Work

Reliable delivery, secure signatures, and full visibility.

Event-Based Delivery

Webhooks fire when things happen: new client, updated instance, workflow created, provider connected, API key issued. React to events as they occur.

HMAC Signatures

Every webhook payload is signed with a secret key. Verify the signature to confirm requests are genuinely from Administrate.

Automatic Retries

Failed deliveries are retried automatically. After 10 consecutive failures, the webhook is disabled and you're notified. Re-enable when your endpoint is back.

Failure Warnings

Get notified after 5 consecutive delivery failures. You'll know there's a problem before the webhook is disabled.

Delivery Logs

See every delivery attempt with status, response code, and timestamp. Debug failed webhooks without guessing.

Flexible Event Selection

Subscribe to specific events or all events. Route different event types to different endpoints.

Full Control Over Event Delivery

Configure, monitor, and debug your webhook integrations.

Webhook Configuration

Webhook Configuration

Set up endpoints with event subscriptions and signing secrets

Delivery History

Delivery History

Track every delivery attempt with status and response codes

Event Types

Event Types

Subscribe to client, instance, workflow, and provider events

Connect Your Systems in Minutes

1

Add Endpoint URL

HTTPS URL where you want events delivered

2

Select Events

Choose which event types to receive

3

Verify Signatures

Use the signing secret to validate payloads

Frequently Asked Questions

What events can I subscribe to?
Client created/updated, n8n instance created/updated, workflow created/updated, LLM provider created/updated, LLM project created/updated, API key created, and webhook created/updated. More events are added regularly.
How do I verify webhook signatures?
Each webhook has a signing secret. We include an HMAC-SHA256 signature in the request headers. Compute the same signature on your end and compare - if they match, the request is authentic. Our docs include code examples for common languages.
What happens if my endpoint is down?
We retry failed deliveries with exponential backoff. After 5 consecutive failures, you receive a warning notification. After 10, the webhook is automatically disabled. You can re-enable it once your endpoint is back online.
Can I have multiple webhooks?
Yes. Create as many webhook endpoints as you need. Different endpoints can subscribe to different events - for example, one for Slack alerts and another for your ticketing system.
Is HTTPS required?
Yes. Webhook endpoints must use HTTPS for security. We don't deliver to plain HTTP URLs.
How quickly are webhooks delivered?
Webhooks are dispatched within seconds of the triggering event. Actual delivery time depends on your endpoint's response time. If your endpoint is slow, deliveries may queue.

Connect Administrate to Your Stack

Set up webhook endpoints and start receiving events in real time.