Type identifier:
flow:triggerCategory: Flow Operations
Entry point for Flow runs. Defines the inputs that a Flow accepts and makes them available to downstream nodes. Every Flow must have exactly one trigger node.
This node has no input handles. It is the entry point of the Flow.
Handle | Data Type | Description |
|---|---|---|
|
| Execution trigger output (unless |
|
| Record data for |
| Varies | Data output for each configured incoming data |
triggertriggerisDataOnly is false. Starts the run.Output handles are dynamically generated based on the incomingData configuration. The handle ID follows the pattern {type}:{incomingDataId} where:
type is the data type (entity, string, number, boolean, date, object, array, file, content)incomingDataId is the unique identifier for the incoming data itemProperty | Type | Required | Default | Description |
|---|---|---|---|---|
|
| Yes |
| Display label for the node |
|
| No |
| If true, the Flow runs in data-only mode |
| array | No |
| Array of incoming data definitions |
isDataOnlybooleanfalseNotes:
true, the Flow runs without a trigger output handleincomingDataid (string), incomingDataId (string), and type; type is one of: entity, string, number, boolean, date, duration, file, object, geojson, array, contententity-type incoming data has additional properties:
Property | Type | Required | Default | Description |
|---|---|---|---|---|
|
| Yes | — | CUID2 of the target Schema |
|
| Yes | — | Display name |
|
| No |
| Whether input is required |
|
| No |
| Show trigger on Record detail view |
|
| No |
| Show trigger on Record table view |
|
| No |
| Auto-trigger on Record creation |
|
| No |
| Auto-trigger on Record update |
|
| No |
| Auto-trigger on Record deletion |
|
| No |
| Display order |
entity-type inputs are enriched with standard Record fields (such as id, createdAt, updatedAt)When isDataOnly is true:
trigger output handle is createdflow:result nodesWhen isDataOnly is false:
trigger output handle starts the downstream nodesRecord inputs can be provided in two ways:
Record lifecycle settings can start the Flow on Record creation, update, or deletion. The lifecycle event supplies the Record ID through the configured Record input. A missing Record produces a null output; when triggerOnDelete is enabled, deleted Records can be included in the lookup.
For Record inputs, the output includes:
id: Record identifiercreatedAt: Creation timestampupdatedAt: Last update timestampcreatedById: Creator user IDupdatedById: Last updater user IDRaw Record values are validated and mapped using the active Schema when the trigger runs. Bare file references in raw Record values are verified when the trigger runs; if verification fails, the run fails.
Scenario | Behaviour |
|---|---|
Missing required input | Error: "No input provided for..." |
Invalid Record data | Error: "Invalid schema data provided for..." |
Schema not found | Trigger run fails |
Record not found (when ID given) | Output is |
Deleted Record with | Deleted Record is included in the lookup |
{
"type": "flow:trigger",
"data": {
"label": "Flow - Trigger",
"isDataOnly": false,
"incomingData": [
{
"id": "input1",
"incomingDataId": "input1",
"type": {
"type": "string",
"display": "text",
"name": "User Name",
"required": true
}
}
]
}
}Output Handles:
trigger (trigger)string:input1 (string){
"type": "flow:trigger",
"data": {
"label": "On Contact Created",
"isDataOnly": false,
"incomingData": [
{
"id": "contact",
"incomingDataId": "contact",
"type": {
"type": "entity",
"schemaId": "clx1234567890abcdefghij",
"name": "Contact",
"required": true,
"triggerOnCreate": true,
"showOnEntity": false
}
}
]
}
}Output Handles:
trigger (trigger)entity:contact (object){
"type": "flow:trigger",
"data": {
"label": "Calculate Total",
"isDataOnly": true,
"incomingData": [
{
"id": "items",
"incomingDataId": "items",
"type": {
"type": "array",
"items": { "type": "number" },
"name": "Items"
}
}
]
}
}Output Handles:
array:items (array) — no trigger handle