SCAIRE

Webhook

Capture and retention settings for inbound webhooks. Trigger sources are managed from the schedule form.

Capture & Retention

Default Auth Mode

Authentication mode pre-selected when creating a new trigger source

Capture Window (seconds)

How long a live-capture session stays open while waiting for a test webhook

Payload Retention (days)

Days to keep raw webhook payloads (0 = never purge)

Coalescing (Debounce + Cooldown)

Coalescing

Batch multiple webhook arrivals within a window into one agent run

Debounce Window (seconds)

How long to collect arrivals before dispatching

Max Batch Size

Dispatch immediately when this many arrive (0 = no cap)

Cooldown (seconds)

After a batch dispatches, suppress further dispatches for this long (0 = no cooldown)

Trigger Sources

Endpoints, recent calls, and activity. Sources are managed from the Schedules page.

Sources

1 active

Calls (24h)

No recent calls

Coalescing

Batching arrivals

Endpoints

Name	Auth	Status
Uptime Kuma https://scaire.bastardgeek.ca/webhook/uptime-kuma	Shared Key	Active

Why Configure Sources

Trigger diagnostics automatically when your monitoring system fires an alert.
Coalesce flapping alerts so one incident runs one diagnostic, not ten.
Every trigger is audited alongside manual and scheduled runs in the Audit Trail.

No sources is fine if you only use scheduled or manual runs from the chat page.

Quick Links

Manage trigger sources and schedules.

Check webhook processing errors.