Overview
A workflow with a webhook trigger now keeps a record of every call it receives, whether or not that call actually started an execution. This makes it possible to see a call gaiia refused or filtered out, not just the ones that ran.
In this article, we'll be covering where to find a workflow's webhook calls, how to filter them, how to view a call's full request and response, and how to view the specific call that started a given execution.
Viewing all webhook calls a workflow has received
Open the workflow and select the clock icon to open Execution History. If the workflow's trigger is currently a webhook, the panel shows two tabs: Executions and Webhook requests.
Select Webhook requests to see every call the trigger has received, most recent first. Each row shows:
- Time & method — when the call arrived and the HTTP method it used
- Status code — the HTTP status code the call was answered with, or a dash if it hasn't been answered yet
- Execution status — the status of the execution the call started, or Triggered no execution if the call was refused or filtered out before an execution could start
The Webhook requests tab reflects the workflow's current trigger. If a workflow is later changed away from a webhook trigger, this tab no longer appears — though calls it already received, and any executions they started, remain individually reachable.
Filtering webhook requests
Use the filter button above the table to narrow the list by:
- Time — when the call was received
- Method — the HTTP method used
- Status code — the status code the call was answered with
- Execution status — the status of the execution the call started, or Triggered no execution for calls that started none
Selecting Triggered no execution clears any selected execution statuses, and selecting a status clears Triggered no execution — a call can't match both at once.
Viewing a call's full request and response
Select any row in the Webhook requests table to open its full detail:
- Request — method, headers, query parameters, path parameters, and body
- Response — status code and body, if the call has been answered
If the call started an execution, a Go to execution button opens it.
Viewing the call that started a specific execution
Any execution that a webhook call started has its own Webhook tab, between Overview and Activity logs, showing the same request and response detail scoped to that one call.
This tab only appears when a call actually started the execution. An execution launched manually or as a test on a webhook workflow has no call to show, so it has no Webhook tab.