Webhooks

Webhooks let the server call an HTTPS receiver of yours whenever a log event you selected happens, with signed JSON and retries. The contract, the envelope and the receiver rules are described in Webhooks in the Automation and AI agents chapter. The feature needs a Professional or Ultimate license.

Global webhooks

The first tab holds the global webhooks: they see every event on the node, the console's own records and those of every virtual site. The list shows name, receiver URL, an enabled switch, the subscription and the last successful delivery on this node, with the actions Edit, Deliveries, Test and Delete.

Test sends a WebhookTest event (9072) to that webhook once, exactly as a real delivery, and shows the receiver's answer and the latency. Deliveries shows this node's counters per process and the most recent failures; every node keeps its own account.

The drawer asks for a name, an optional description, the enabled switch, the receiver URL (absolute HTTPS unless the policy allows plain HTTP), the secret that signs the deliveries (required on creation, never shown again, left as it is to keep it), an optional authorization header sent verbatim, the events (single events or whole blocks, searched by name, number and description), the minimum level, and the advanced settings: timeout, retries, queue size and whether the webhook may target a private address, which the policy must allow as well. Loopback is never allowed.

Virtual sites

The second tab lists a chosen site's webhooks for oversight. They are created and managed by that site's Admins, under the site's Webhooks permission.

The policy

Under Global Configuration, Advanced settings, Webhooks you decide what a webhook may target and the limits: whether private addresses and plain HTTP are allowed at all, how many webhooks each scope may have, how long delivery records are kept on each node, and the largest queue a webhook may ask for. See Global Configuration.

The live event stream

The Events page shows the events of this node as they happen, filtered by block, level and virtual site, with the workers' events included. It is a window on the log, not a record: close it and nothing is kept. The API behind it is described in The live event stream.