Update
Change existing named variables wherever they already live.
Type
ctx.vars.update Block Context
Folder
basic/contextChannels
Any
Pipe
Value
Scope
Any
Update (palette name Update) changes named variables that already exist. It writes on the nearest owner of that name (this body, or an outer loop/workflow scope). It does not create a new name. If a key is missing, the block fails with Variable not found.
Use Set (or the Variables list on Start / Lambda) to create the name first.
Each row is a Key plus a Value (fixed or a context path). The same object is written to the data pipe.
Configure
| Setting | Description |
|---|---|
| Key | Existing name other blocks already use (for example customerId). Same naming rules as Set. |
| Value | Literal or a variable path from this block’s context |
| Add variable | Appends the row |
Add as many rows as you need. Duplicate keys are ignored.
Handles
| Handle | Role |
|---|---|
| In (target) | Incoming connection |
| Out (source) | Continues after the names are updated |
Pipe schema
The next block reads this on the data pipe (pipe.value).
| Field | Type | Description |
|---|---|---|
| Updated variables | object | One property per Key, with that row’s resolved value |
Downstream blocks can also bind the names directly.
Use case
- After creating
totalon the main path, update it inside a loop so the main path still sees the new total. - Set flags that later conditions on the main graph should see.