Skip to main content
Use dynamic values to fill a step’s inputs with data from the trigger or from earlier steps, so each run works with the ticket, person, or record that started it.

Insert a dynamic value

Click a field input in a step and choose a value from the picker. The picker lists the data available to that step, grouped by the step it comes from. Values resolve when the workflow runs, not when you build it.In text fields, such as a message body or a ticket title, you can mix dynamic values with your own text, for example Laptop request for followed by the requester’s name.

Trigger data

The trigger exposes information about the event that started the run. For ticket triggers this includes ticket properties (title, description, priority, status, identifiers), requester details (name, email), custom field values, Slack thread data, and timestamps. Other triggers expose their own data, such as the asset for asset triggers or the tags that changed for Ticket Tags Changed.Example: Include the Slack thread link in a webhook payload so an external system can link back to the original conversation. Choose Ticket > Slack > Thread > Link.

Ticket identifiers

Tickets expose three identifiers. Use the one your message or downstream system expects:Example: Put the Display ID in a Slack message so the recipient sees BUGZ-123 instead of an internal ID. Choose Ticket > Display ID.Example: Append the Short ID to an external URL (https://example.com/?ref=abc12345) to correlate the ticket later without exposing the channel prefix. Choose Ticket > Short ID.

Email details

Tickets created from expose an Email Details group in the value picker, filters, and conditions. The values are empty on tickets created any other way.Example: Several addresses, such as it@acme.com and emergency.it@acme.com, route into one channel. Add a condition on Ticket > Email Details > Sent To to raise the priority of tickets sent to the emergency address.

Action outputs

Most actions return data that later steps can use, such as the ID of a created ticket, a Jira or Linear issue key, an Okta user, a Slack thread link, or an HTTP response. Many also return Is Success, which you can check in a condition.Example: After Create Jira Issue, use Link Ticket with the issue’s URL to attach it to the original ticket.Each action’s outputs are listed on the actions page.

Loop items

Inside a Loop, the picker adds the current item, shown as Loop > followed by the item type, and Loop Info, which holds the item’s position (Index), the number of items (Size), and the number of iterations that will run (Limit).

Which values a step can use

A step can only use values from steps that run before it on the same path:
  • Upstream steps only. The picker offers the trigger and the steps above the current one. You can’t reference a step that runs later.
  • Parallel branches can’t see each other. Two steps on separate parallel paths can’t reference each other’s outputs.
  • Converging steps see every parent. A step that several paths lead into can reference all of them, but values from a path that didn’t run, failed, or was skipped are empty.
The builder flags a reference to a step that isn’t upstream, and the workflow can’t be published until you fix it.
A value that can’t be found at run time resolves to empty. Inside text it becomes blank, and a required field left empty makes the step fail. Check the step’s resolved inputs in the run log to see what each value became.
Last modified on November 18, 2026