Workflow node reference
Update Contact
Update contact information or custom fields. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Update Contact workflow node.
What this guide covers
- Category: Actions.
- Use it to persist mapped name, email, custom, or other supported contact fields.
- 2 configuration fields and 3 documented outputs.
- Do not overwrite reliable profile data with unvalidated AI output.
What this node does
Update contact information or custom fields
Use it to persist mapped name, email, custom, or other supported contact fields.
When not to use it
Do not use it just to keep a value inside one execution; use Set Variable.
Prerequisites
- Current contact context
- Valid Fields to Update JSON
- Source variables available before this node
Current contact context. Valid Fields to Update JSON. Source variables available before this node
Inputs and configuration fields
| Field | Key | Control / type | Requirement | Default | Accepted values and behavior |
|---|---|---|---|---|---|
Fields to Update | updates | json | Required when shown | No default | Map field names to values. { "name": "{{nodes.ai_extract.extracted.name}}", "custom.company": "{{nodes.ai_extract.extracted.company}}", "custom.last_inquiry": "{{system.date}}" } |
Create Custom Fields if Missing | create_if_missing | toggle | Optional | true | Value accepted by the displayed control |
Configure the node
- Drag Update Contact 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.update_contact.success}} | boolean | Whether update succeeded |
{{nodes.update_contact.updated_fields}} | array | List of fields that were updated |
{{nodes.update_contact.contact}} | object | Updated contact data |
Execution behavior
- Resolves the update map.
- Optionally creates missing custom fields when enabled.
- Emits success, updated field names, and the updated contact object.
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
Store extracted company and last inquiry date on the current contact.
Message Received → Extract Info → Condition → Update Contact → Add NoteCommon errors
| Symptom | Resolution |
|---|---|
Update JSON is invalid | Use a JSON object mapping field names to values. |
A field is empty | Inspect the preceding node output in Test. |
Limitations
Do not overwrite reliable profile data with unvalidated AI output.
Supported persistent fields depend on the contact model.
Do not overwrite reliable profile data with unvalidated AI output. Supported persistent fields depend on the contact model.