new
Automations
Now Available
Pull exact data from automations to inform subsequent steps in the workflow
Grab the specific piece of data you need from a previous automation step with the new "Extract value" field. Pull a contact name, an email address, an item count, etc. and pass it cleanly into the next step.
Clean data in, clean data out
When you add dynamic content from a previous step, you'll now see an optional "Extract value" field. Enter a path expression to pull out exactly the value you want from that step's output, and use it directly downstream.
What you can do with expressions:
- Extract nested fields:.data.results[0].name
- Count items:.items | length
- Combine fields:"\(.first_name) \(.last_name)"
- Filter arrays:.items | map(select(.active == true))
Example:
A third-party booking app sends a webhook with nested contact details. Use expressions like .data.contact.first_name
and .data.contact.email
to extract just the fields you need and automatically create a contact—no manual data entry, no raw JSON to untangle.Why this matters
Automations frequently need to hand data from one step to the next, but until now, that meant passing along the full output of the previous step, often as nested raw JSON. Downstream steps had to work around extra fields, or you had to manually parse the payload before it could be used.
The result: automations that were harder to build, harder to read, and harder to maintain when upstream data shapes changed. Now, you can pull out exactly the field you need in one step; no developers required.
Who it's for
- Partners building automations that consume webhook payloads, API responses, or nested data
- Any team that's been working around raw JSON in downstream steps
- Partners who've needed a developer to parse payloads before they could be used in an automation