Trigger node
The Trigger node is the automatic entry point of your workflow: added when the workflow is created, it cannot be deleted and is the first node executed. It represents the trigger associated with the workflow and the data it receives.
Parameters
The Trigger node generally requires no configuration, as it is automatically configured according to the trigger associated with the workflow.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| No manual configuration | — | ✅ | — | The node is auto-configured from the workflow's trigger. |
Displayed information
The node displays:
- The trigger name
- The trigger type
- The data available in the context
Input
The node receives the data from the trigger associated with the workflow. Depending on the trigger type, the input information is exposed in the following form:
{
"incomingRequest": {
"method": "POST",
"url": "https://api.example.com/orders/4821?lang=fr",
"query": {
"lang": "fr"
},
"params": {
"id": "4821"
},
"headers": {
"content-type": "application/json"
}
},
"data": {
"orderId": "4821"
}
}
- HTTP method (for API route) →
incomingRequest.method - Full request URL →
incomingRequest.url(e.g.https://api.example.com/orders/4821?lang=fr) - Request body →
data - Query parameters (query string) →
incomingRequest.query - Path parameters (dynamic segments of the Path) →
incomingRequest.params - HTTP headers →
incomingRequest.headers - File information (for File) →
dataandcontext.filename - Message ID (for AWS SQS) →
incomingRequest.messageId
Output
The Trigger node performs no transformation: the received data is exposed as-is in the workflow context and is accessible from the following nodes.
{
"data": {
"orderId": "4821"
},
"incomingRequest": {
"method": "POST",
"url": "https://api.example.com/orders/4821?lang=fr"
},
"context": {
"filename": "facture.pdf"
}
}
For a File trigger, the name of the received file is exposed in context.filename.
Example
Resend the received body
In a following HTTP(S) Request node, to resend the received body for example:
{
"url": "https://api.example.com/process",
"method": "POST",
"body": {
"payload": "{{data}}"
}
}
Retrieve a path parameter
For an API route trigger with path /orders/:id, retrieve the identifier captured in the path:
See API route — Customize the Path for the parameter syntax (:id, :id?, *path) and the access via incomingRequest.params.