Workflow node reference
Assign Tag
Add or remove tags from contact. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Assign Tag workflow node.
What this guide covers
- Category: Actions.
- Use it to add or remove a selected, newly named, or variable-derived tag on the current contact.
- 5 configuration fields and 3 documented outputs.
- The Contacts UI does not expose a separate bulk tag manager.
What this node does
Add or remove tags from contact
Use it to add or remove a selected, newly named, or variable-derived tag on the current contact.
When not to use it
Do not use it to change contact profile fields or maintain a full external CRM taxonomy.
Prerequisites
- Current contact context
- Existing tag, valid new tag name, or variable value
Current contact context. Existing tag, valid new tag name, or variable value
Inputs and configuration fields
| Field | Key | Control / type | Requirement | Default | Accepted values and behavior |
|---|---|---|---|---|---|
Action | action | select | Optional | add | Add Tag (add), Remove Tag (remove), Toggle Tag (toggle) |
Tag Source | tag_source | select | Optional | select | Select existing tag (select), Create new tag (create), From variable (variable) |
Tag | tag_id | select | Optional | No default | shown when tag_source equals select |
New Tag Name | new_tag_name | text | Optional | No default | shown when tag_source equals create |
Tag Variable | tag_variable | variable-input | Optional | No default | shown when tag_source equals variable. Variables supported |
Configure the node
- Drag Assign Tag from Actions in the node palette.
- Select the node to open its configuration drawer.
- Complete every required field and any conditional field revealed by your choices.
- Insert variables only from the current trigger or an earlier node on the same path.
- Connect every required output handle to the intended next step.
- Save and run Workflow Test with representative data before activation.
Outputs
Later nodes can use these values only after this node has run successfully on the same execution path.
| Variable | Type | Meaning |
|---|---|---|
{{nodes.assign_tag.success}} | boolean | Whether tag operation succeeded |
{{nodes.assign_tag.tag_name}} | string | Name of the tag |
{{nodes.assign_tag.action_taken}} | string | What was actually done |
Execution behavior
- Resolves the tag source and requested add/remove action.
- Updates the current contact.
- Emits success, tag name, and action actually taken.
Do not assume a failed node is automatically retried. Review the execution result and the relevant service documentation before repeating an operation that could create a duplicate side effect.
Example use case
Add vip-customer after a qualification condition passes.
Classifier → Condition → Assign Tag → Notify Team → End FlowCommon errors
| Symptom | Resolution |
|---|---|
No current contact | Use a conversation/message trigger that supplies contact context. |
Tag source is empty | Select a tag or confirm the variable resolves. |
Limitations
The Contacts UI does not expose a separate bulk tag manager.
Tag changes apply to the current contact only.
The Contacts UI does not expose a separate bulk tag manager. Tag changes apply to the current contact only.