Add contact to automation

Identifier and availability

• Type: action
• Stable identifier: workflow:enroll_contact
• Status: Selectable — available in the new-node selector and importable.

Purpose

Adds the current contact to another automation.

Prerequisites and context

Required configuration: target_automation. Runtime requires a contact in context.

Parameters

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_workflow_enroll_contact",
    "branch": "actions",
    "order": 1
}

Valid JSON node example

{
    "key": "action_workflow_enroll_contact",
    "type": "action",
    "name": "workflow:enroll_contact",
    "display_name": null,
    "parameters": {
        "target_automation": {
            "automation_key": "follow_up"
        }
    }
}

Validation and runtime caveats

An Automation cannot enroll a contact into itself. Avoid cycles between multiple Automations.

See the Automation JSON import format for the envelope, dependency resolution, graph rules, complete examples, and AI author checklist.