Outbound Webhooks
Pipe execution results into your own systems — a logging service, an incident tool, or a custom dashboard. After every run, QuzenixCron POSTs a JSON event to your endpoint. Available on the Business plan.
Setup
Go to Settings → Outbound Webhook, enter your endpoint URL, and save. We send a test event immediately and only save the URL if your endpoint responds, so a typo can't silently break delivery.
Event payload
A POST with Content-Type: application/json is sent after each execution finishes (scheduled or manual):
{
"event": "job.execution.finished",
"created_at": "2026-06-06T09:00:00.000Z",
"job": {
"id": "…",
"name": "Nightly backup",
"url": "https://api.example.com/backup"
},
"execution": {
"id": "…",
"status": "success",
"http_status": 200,
"duration_ms": 412,
"error_message": null,
"is_manual": false
}
}Delivery is best-effort
Outbound webhooks are fire-and-forget — we don't retry delivery, and a slow or failing endpoint never blocks or fails the job itself. For guaranteed history, rely on execution logs and the CSV export in Audit Logs.HTTPS and public URLs only
The endpoint must use https:// and resolve to a public host. Localhost and private/internal IP ranges are rejected for security.