Inspect a delivery

Inspect a delivery

Every row in Webhook Logs is one delivery attempt. Click anywhere on the row to expand a detail panel showing the full request and response. The detail is lazy-loaded — bodies are fetched on first expand, not on page load, so a long log doesn't slow the table.


What each row shows

Column

Means

Column

Means

☑

Multi-select checkbox — only present if the row is eligible for replay.

▸

Expand chevron. Clicking anywhere on the row also toggles it.

Webhook

Name of the webhook that produced this delivery. Click-through opens the webhook in edit mode.

Event

Coloured event-family badge (Issue / Comment / Worklog / Project / …). Scheduled deliveries show an automation icon.

Status

HTTP status lozenge + a Replayed marker with timestamp if applicable. Colours: green 2xx, blue 3xx, amber 4xx, red 5xx / Network, neutral Skipped.

Initiator

Avatar + display name of the Jira user whose action triggered the event. Scheduled deliveries show the automation icon.

Execution

Round-trip time in ms. Colour-coded — green = fast, amber = slow.

Date

UTC timestamp of the delivery.

Action

Run again button when eligible, plus a warning triangle if the failure looks permanent (e.g. 401 Unauthorized).


Expanding a row

Click anywhere on the row, or the chevron. The detail panel opens beneath the row with two sections.

Request

  • Webhook URL — with the HTTP method badge.

  • Query — two-column table of URL parameters sent.

  • Header — request headers Webhooks Pro added (your own; system headers aren't persisted).

  • Body — the rendered payload JSON. Pretty / Raw toggle switches between formatted and as-sent. Copy payload button copies to clipboard.

Response

  • Header — response headers the receiver returned.

  • Body — response body, pretty-printed when JSON.

  • Error — if the delivery failed at the network layer (no HTTP response), this section replaces Header + Body with the receiver-side error message in a red banner.


Reading the detail like a pro

Always start with the Status

If you see

Likely cause

If you see

Likely cause

Green 2xx

Working. Compare the body vs. what the receiver should have done.

Blue 3xx

Receiver redirected. Webhooks Pro doesn't follow redirects automatically — you may need to update the URL.

Amber 4xx

Receiver rejected the request. Read the response body first — most APIs say what's wrong.

Red 5xx

Receiver had an internal error. Check the receiver's own logs, then replay.

Red Network Error (0)

No response — timeout, DNS, refused, or egress not approved. See Status code 0 and network errors.

Neutral Skipped — license …

Webhooks Pro intentionally did not send. Renew the licence.

Then the response Body

Most receivers tell you exactly what's wrong:

  • Slack: {"error": "invalid_payload"} — your JSON is malformed or has the wrong content-type.

  • GitHub: {"message": "Bad credentials"} — your Authorization header is wrong.

  • Generic: {"error": "missing field 'foo'"} — your template doesn't produce what the receiver expects.

Compare Request Body vs receiver expectation

Open the request body. Toggle to Pretty for readability. Match it field-by-field against your receiver's spec.

Common mismatches:

  • Receiver expects {"text": …}, your template produces {"message": …}.

  • Receiver expects an array, your template produces an object.

  • Receiver expects a number, your template produces a string (because you didn't use whole-quote substitution).

The fix is in the Custom JSON template.

Check the headers

Authorization, Content-Type, custom headers — they're all in the Request → Header table. If any are missing or wrong, fix them on the webhook form.


Replay grouping

When you click Run again, the replay is saved as a new log row with sourceLogId pointing back to the original. The UI shows replays:

  • Indented under their parent.

  • With a blue left border and a ↳ glyph in the checkbox column.

  • Both parent and children appear on the same page so you see the full history at a glance.

Enable Hide replayed (top of the page) to collapse each chain and only see the freshest attempt.

Full reference: Replay a delivery (Run again).


Initiator: who triggered this?

The Initiator column shows the avatar + display name of the Jira user whose action produced the event. Useful when:

  • Auditing changes — "who triggered the webhook that updated the dashboard?"

  • Debugging permission issues — sometimes a webhook fires under an unexpected account.

For scheduled deliveries, there's no human initiator — the row shows an automation icon instead.

For post-function deliveries, the initiator is the user who clicked the workflow transition.


Date and time

Always UTC. The timestamp shown is when Webhooks Pro made the HTTP request, not when Jira fired the event (those differ by the debounce window — see Debounce and coalescing).

If you need millisecond precision, expand the row — the response timing in milliseconds is in the Execution column already.


What's not in the detail

  • The original Jira event payload — Webhooks Pro doesn't keep the raw event after rendering the template. The template's output is the source of truth.

  • System headers added by Webhooks Pro (X-Webhook-Event, X-Webhook-Timestamp, X-Webhook-Agent, default Content-Type) — they're deterministic and identical on every delivery, so they're not persisted to save space.

  • Receiver IP / TLS details — Forge sits in front; the app doesn't see the network layer below HTTPS.

  • The signing secret — only the resulting X-Webhook-Signature header is part of system headers (not stored). The secret itself is never logged or echoed.


Related