Using data from an earlier step in an automation no longer means typing or copying {{...}} paths. Click + or type @ in any input field, browse the steps that come before it, and pick the field you need. The new property picker is available now.
What is new
- In every input field. Click + or type @ in any field of a step to open the picker.
- Only steps that have run. The picker lists only the steps that are guaranteed to have run before the current one, with every field they output and its type: text, number, date, yes/no, list, or object.
- Browse nested data. Objects open as levels you click into, such as a customer with a contact and an address, with a breadcrumb to go back up. You can also insert a whole object or list at once.
- Readable chips instead of raw paths. A picked field shows as a chip with a readable name. Use the { } toggle when you want to see the raw value.
- Broken references are flagged. If a field you picked no longer exists, for example because the earlier step changed, the field is flagged in the builder instead of silently sending an empty value.
- The same references in the Tekst MCP. When you build or change automations with an AI assistant through the Tekst MCP, it uses exactly the same list of fields as the picker.
Why it matters
Reusing a value from an earlier step used to mean knowing its exact path, copying it from another automation, or even adding a code step just to expose it. Nested data, like a list of order lines, was the hardest part to get right. With the property picker, the right value is a click away, so your team can change and extend automations on its own, with less trial and error and fewer automations that break without anyone noticing.
Getting started
Open an automation, select a step, and click + or type @ in one of its fields. New to automations? Start with What are automations?.
0 comments
Please sign in to leave a comment.