Skip to main content
On the graph, add Update records. On an agent, open State and turn Update records on. Update records changes the same fields on every record that matches a filter, or on one record by its id. Other fields stay as they are. To add records or replace a whole record, use Save records.

Filter and values

Connect a previous node — usually Code — that returns:
This sets status to C on every record in rates whose lane is E. One record by its id:
This sets status to sending on the record whose id is row-1. key is that record id. Read records returns it as key. Inside a Loop, Insert value on Key inserts {{Loop name.item.key}}. A field inside the record is not this id. A where path key reads a field named key in the record. The id follows the State key rules. Pass key, where, or both. Both means this id and the filter. where with no condition and no key is an error, not every record. An id that is not in the collection succeeds with Updated 0 and does not add a record. where uses the same filters as Read records. set is the new value for each field. If you set an object, it replaces what was there. Field names are dotted keys (status, price.amount). If this JSON already has collection, you can leave Collection empty on this node. Key works the same way: an empty Key uses key from the previous Result. Where and Set are Previous node or On this node. Previous node uses that value from the previous Result. On this node replaces it with the rows in the inspector. The other keys still come from the previous Result. Removing every row returns to Previous node. On this node with no Where rows ignores where from the previous Result, so set a Key or add a filter. An Agent can send the same key, where, and set when it uses this tool. A value filled on the tool is fixed and is not sent by the Agent. Fixed with no Where rows ignores where from the Agent. Set cannot be fixed with no rows.

Input

Inspector Settings. Empty-field rules for the Graph: Previous nodes. Insert value is on Key, Where, and Set. On an Agent Tool, Collection, Key, Where, and Set can be Agent decides or Fixed. The step still needs a key or a where, and a set, from this node or from the previous Result. An empty where with no key is an error, not every record.

Output

On the next node, Previous nodes lists Update records: Result ({{Update records.text}} while the name is unique).

Limits

At most 8 filters in where and 8 fields in set. New values together may be at most 64000 bytes. At most 5000 matching records. If more match, the step fails and writes nothing. Run the same set again with a tighter where, then the next slice, until every group is at or under 5000. Example — 8000 rows across two lanes, same new status:
If one value still matches too many, add another field (eq, in, or a range gte / lt). If a field cannot be written because a value on the way is not an object, the step fails and writes nothing. Example: setting price.amount when price is already the string "flat". If the collection has a schema, each new value must match that field. A mismatch fails and writes nothing.