Events

Everything moving in and out of your customers' systems, newest first.

Activity → Events

Auto refresh, top-right, is off by default.

An event is one inbound arrival: a webhook fired, a schedule reached, or a manual run. This is the first place to look when something did not happen.

The table

Column	Notes
Event	The event identifier.
Source	Where it came from: webhook on every row observed.
Status	Delivered on a successful hand-off.
When	Timestamp, in your timezone.
Replay	Re-delivers the row. See below.

Filter chips carry live counts (All, Webhook, Scheduled, Manual) so you can see at a glance whether your schedules are firing. Search events narrows the list.

The list is not paginated, and rows do not expand. To see what a run did with an event, go to Executions.

Auto refresh

The toggle top-right is off by default. Turn it on to keep the list current without reloading (useful while you are testing a webhook from the sending system) and off again when you want to read a stable list.

Replay

Every row has Replay, which re-delivers the same payload to the same workflow. Use it after fixing a workflow that failed on an event you cannot ask the sender to resend.

Replay re-runs the workflow for real. If the workflow writes to an external system, and it has no deduplication key, replaying can create duplicates. Set a deduplication key on the webhook trigger before you need it.

An event that exhausts its delivery attempts shows a failure state in the Status column and can be re-sent with Replay once the cause is fixed. Attempt count and backoff are configured on the trigger, not here.

When nothing is listed

An empty filter gives you Nothing matches that filter, with:

Events arrive as your customers use their connected systems. Widen the filter, or check that a trigger is listening.

and a Show all events button. Take the second half of that literally: an empty Events log with a trigger you expected to fire is a trigger problem, not an events problem. See Triggers.

Events versus executions

An event is something arrived. An execution is a workflow ran. One event can produce several executions when a webhook fans out to multiple routes, and an event can be Delivered while the execution it started fails. Check both.