core / trigger / schema v1
Webhook
Trigger workflow via HTTP request
Prerequisites
No connection prerequisite is declared for this node.
Parameters
| Parameter | Type | Description |
|---|---|---|
HTTP Methodmethod | select Optional | Which HTTP method your webhook URL accepts. "Any" works for most services; restrict it if you want stricter validation. Options: Any (), POST (POST), GET (GET), PUT (PUT) |
Secret Tokensecret | text Optional | Optional but recommended: requests must carry this value in the X-Webhook-Secret header or they are rejected. Stops strangers who find your URL from triggering the workflow. |
Inputs and outputs
Inputs
No ports declared.
Outputs
on_request- On Request (output)body- Body (output)headers- Headers (output)query- Query (output)method- Method (output)ip- Remote IP (output)requestBody- Body (this webhook) (output)requestHeaders- Headers (this webhook) (output)
Output data schema
[
{
"key": "method",
"type": "string",
"label": "HTTP Method",
"example": "POST"
},
{
"key": "receivedAt",
"type": "timestamp",
"label": "Received At"
},
{
"key": "body",
"type": "object",
"label": "Body",
"description": "The request body: shape depends on whoever calls your webhook"
},
{
"key": "headers",
"type": "object",
"label": "Headers",
"description": "Request headers (sensitive ones removed)"
},
{
"key": "query",
"type": "object",
"label": "Query Parameters"
}
]Examples and troubleshooting have not yet been reviewed for this contract.
Version and compatibility
This reference follows the current authoring contract. Existing workflows retain their saved node revisions.
Contract identifier
cbe357a56fd800b4326a022bf3c51ad80755e0680c3cc33de99f1c4621659942