Update Customer
Set customer nickname, email, or phone from workflow variables.
The Update Customer action writes customer profile fields using optional variable bindings. Each field has its own tree picker—no free-text literals in the form.
When to use
- Normalize phone or email collected in an earlier message step.
- Set System Name (nickname) from CRM or HTTP response variables.
- Enrich profile after HTTP Request or Fireberry returns data.
Configuration
| Field | What it does | When to use |
|---|---|---|
System Name (customerNickname) | Bind nickname from upstream variable/expression | Display name overrides |
| Bind email | Capture from user input variable | |
| Phone Number | Bind phone | Sync number from trigger or form answer |
| Description | Canvas note | Team notes |
All three fields are optional. Clearing a picker clears that binding. Each field accepts a fixed value from upstream nodes or an expression, depending on what the picker offers.
Flow behavior
- Input: Nodes that expose customer or custom variables (Variables).
- Output: Single edge.
- Unset fields are not updated at runtime.
Examples
Save email from survey answer
- WhatsApp with Wait for user response and answer sub-node.
- Update Customer → Email ← variable from answer node output.
Nickname from Fireberry
- Fireberry fetch/update.
- Update Customer → System Name ← Fireberry name field variable.