User added to team

Identifier and availability

• Type: trigger
• Stable identifier: user_assigned_team
• Status: Selectable — available in the new-node selector and importable.

Purpose

Starts when a user is added to a team.

Prerequisites and context

Required configuration: team. Review the available context below before using variables.

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

Trigger context groups: team, user.

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_user_assigned_team",
    "branch": "trigger",
    "order": 1
}

Valid JSON node example

{
    "key": "trigger_user_assigned_team",
    "type": "trigger",
    "name": "user_assigned_team",
    "display_name": null,
    "parameters": {
        "team": {
            "name": "Sales"
        }
    }
}

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.