Move contact to pipeline status
Identifier and availability
- Type:
action - Stable identifier:
move_to_pipeline_status - Status: Selectable — available in the new-node selector and importable.
Purpose
Moves the contact to a selected pipeline status.
Prerequisites and context
Required configuration: pipeline, pipeline_status. Runtime requires a contact in context.
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
This node declares no additional variable groups. The always-available date group and context inherited from its path still apply.
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
This is a sequential action with no branch ports. A root placement uses from set to null and branch set to actions; a branch placement uses the branching action key and branch token. Use a 1-based order within that path.
Connection fragment:
{
"from": null,
"to": "action_move_to_pipeline_status",
"branch": "actions",
"order": 1
}
Valid JSON node example
{
"key": "action_move_to_pipeline_status",
"type": "action",
"name": "move_to_pipeline_status",
"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.