All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Update fields on a record or its linked records

The Change the record step changes fields in the trigger record, in records linked to it, in a specific record, or in a record a find step found. It also sets assignees and relations.

7 min
Before you start · for owners and managers
The permission to edit workflows
  • You need: The permission to edit workflows

Steps

1
Press Add a step and choose Change the record.
2
Under Which record, choose the target record (see the table below).
3
Under Set these fields, choose the fields and write their values, or press Use a detail instead.
4
Optional: under Set a link from this record, press Add a link to set a relation from the trigger record’s relations.
5
Try it with a Practice run: it shows what the step would change, without writing anything.

Which record is updated?

Target
When to use it
This record
The trigger record; the most common
A record linked to it
All the records linked to the trigger record through a relation you choose, up to 200 records
A record I pick
One record you choose by name; useful for triggers with no record
The record a Find step found
The record a Find a record step found

Kinds of values

Field
How the value is written
Text, number and date
A fixed value, or a variable such as {{today}}
List, status and priority
Choose an option that exists in the field
Assignees
Choose active members; they replace the record’s assignees

Setting a relation from the trigger record’s relations

Example: “When a payment is created, link it to the same client as the invoice.” You choose a path of one or two relations, and the record at the end of the path is linked.

If there’s more than one record on the path, Use the newest picks the most recently linked one, and Stop the step makes the step fail.

No relation is ever cleared: an empty path skips the linking. A record that’s already linked stays as it is, unless you turn on Replace an existing link.

Protecting your data

A value made only of empty variables isn’t written, so a mistake in a variable name doesn’t wipe the field.

Every record is checked before the first write. If one is refused, nothing is written, and the refused record is shown.

The update is written only once, even if the step is retried.

The change doesn’t start another automation.

If something goes wrong

What you see
Why
What to do
“Invalid status. It must be one of...”
The chosen option was deleted from the field.
Choose the option again in the step.
“… is not an active member of this workspace.”
The member was deleted, deactivated, or is from another workspace.
Choose an active member.
“The target record isn’t set”
A message trigger, and the chat isn’t linked to a record.
Link the channel to a unit. See How a chat becomes a client record.
“Several records are linked along the path to …, and this step is set to stop in that case.”
The relation holds several records, and you chose to stop.
Choose Use the newest instead of Stop the step.

A real example

Namaa Academy
The situation

The academy wants to see which clients wrote back.

What they did
  1. The trigger A message arrives from a linked client.
  2. Change the record: set the “Status” field to “Replied”.
  3. Notify a team member: tell the record’s owner.
The result

The salesperson sees the engaged clients without following up by hand.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Up to 200 linked records in one step.
Relation path: one or two relations.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.