Contact added to pipeline status
Identifier and availability
- Type:
trigger - Stable identifier:
pipeline_status_added - Status: Selectable — available in the new-node selector and importable.
Purpose
Starts when a contact reaches a pipeline status.
Prerequisites and context
Required configuration: pipeline, pipeline_status. Review the available context below before using variables.
Parameters
| JSON path | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
pipeline |
pipeline_reference | Yes | — | — | Exact Pipeline name in the importing tenant. |
pipeline_status |
pipeline_status_reference | Yes | — | — | Exact Pipeline Status name within the selected Pipeline. |
Unknown parameter and settings keys are rejected. Resource references use names, emails, document keys, or endpoints rather than database IDs.
Inputs and available variables
Trigger context groups: contact, pipeline, pipeline_status.
Templated strings use double braces, for example {{contact.first_name}}. Availability in the editor does not create runtime context; the trigger and preceding branch still need to provide it.
Connections and branches
When used, this node must be the Automation’s only root trigger. Connect it with from set to null and branch set to trigger. It cannot be a branch child.
Connection fragment:
{
"from": null,
"to": "trigger_pipeline_status_added",
"branch": "trigger",
"order": 1
}
Valid JSON node example
{
"key": "trigger_pipeline_status_added",
"type": "trigger",
"name": "pipeline_status_added",
"display_name": null,
"parameters": {
"pipeline": {
"name": "Sales"
},
"pipeline_status": {
"name": "New Lead"
}
}
}
Validation and runtime caveats
The node runs only after its Automation is explicitly reviewed, published, and active.
See the Automation JSON import format for the envelope, dependency resolution, graph rules, complete examples, and AI author checklist.