Event Log

Overview

Every webhook event is logged with its full payload, status, timing, and metadata. The Event Log lets you view, filter, search, export, retry, and replay events.

Viewing Events

Open a webhook connection and click the Events tab. Each event shows:

• Timestamp — when the event was received
• Event type — extracted from the payload (e.g., "payment_intent.succeeded")
• Source — where the event came from
• Status badge — color-coded result

Status Badges

Badge	Color	Meaning
OK	Green	Event processed successfully
Error	Red	Processing failed (see error details)
Queued	Amber	Received while connection was paused, waiting to be processed
Skip	Gray	Event was skipped (e.g., filtered out by rules)

Filtering Events

Use the filter bar above the event list to narrow down what you see:

• Status — Show only Success, Error, Skipped, or all
• Event Type — Filter by event type (dropdown auto-populates from your events)
• Event Source — Filter by source (dropdown auto-populates from your events)
• Search — Free text search across event data

You can also change how many events are shown: 25, 50, 100, or all (up to 500).

Expanding Event Details

Click any event row to expand it and see the full details:

Metadata Grid

A summary grid showing:

• Timestamp — exact time the event was received
• Source IP — the IP address of the sender
• Processing Time — how long it took to process (in milliseconds)
• User Agent — the HTTP client that sent the request

Error Details

If the event failed, a red error box shows the error message with an explanation of what went wrong.

Payload

The full JSON payload is shown in a scrollable, pre-formatted code block. This is exactly what the external service sent.

Field Mapping Results

If you have field mapping configured, you'll see:

• Mapped fields — which source fields were successfully written to your table, with the values
• Failed mappings — which fields couldn't be mapped, with the reason
• "How to Fix" tips — contextual help for common mapping and token errors

Extra Metadata

Any additional metadata attached to the event (beyond the standard fields) is shown as formatted JSON.

Retrying Failed Events

When an event has an Error status, a Retry button appears in the expanded details. Click it to reprocess the event with the same payload.

This is useful when:

• You've fixed a field mapping issue and want to re-run the event
• A temporary error (timeout, rate limit) caused the failure
• You've updated your destination table and want to try again

Replaying Events

Any event (regardless of status) can be replayed. Click the Replay button to create a new event from the existing payload and process it fresh.

Replay differs from retry:

• Retry reprocesses the same event record
• Replay creates a new event record from the same payload

Use replay when you want to test changes to your field mapping without modifying the original event's status.

Exporting Events

Click Export CSV to download your filtered events as a CSV file. The export includes:

Column	Description
timestamp	When the event was received
type	Event type
source	Event source
status	success, error, skipped, or queued
error	Error message (if any)
processing_ms	Processing time in milliseconds
source_ip	Sender's IP address

The export respects your current filters — only the events you can see are exported.

Clearing Events

Click Clear Logs to delete all events for this connection. A confirmation dialog asks you to confirm because this action cannot be undone.

Use this when you want a clean slate after testing, or to remove old data that's no longer relevant.

Tips

• Use the Status filter to quickly find failed events that need attention
• Export CSV before clearing logs if you want to keep a record
• Replay is great for testing field mapping changes without waiting for new events from your external service
• Check the Processing Time to identify slow events that might indicate mapping complexity