DashboardSign inStart your trial

In this guide · BuildClose guide

Use Data from Earlier Steps

Add information from an earlier workflow step without writing code.

A step can use information that an earlier step received or created. For example, an email trigger provides the sender and subject, an AI step provides a draft, and a form provides the answers someone submitted.

You do not need to copy values between steps or write code. Rills fills in the value for each workflow run.

#Insert a value

  1. Click in the field where you want the information to appear.
  2. Select Insert data from an earlier step.
  3. Choose the earlier step, then choose the detail you need.

Rills adds the selection as a labeled chip. The chip is a placeholder: when the workflow runs, Rills replaces it with that run’s actual value.

For example, to address a reply to the person who emailed you, select the email trigger, then choose Sender in the To field. To reuse the email’s subject, type Re: in Subject, then insert Subject from the same trigger.

#What you can choose

The picker only shows information available before the step you are editing. Connect a step to the workflow path first if its output is missing.

Common choices include:

  • Details received by the trigger, such as a form response, incoming email, or app event
  • Results from an AI, data, or connected-app step
  • A response a reviewer entered in a Human Review step
  • The current item inside a loop

Select a step to see its available details. A structured AI result, for example, may offer separate Subject, Body, and Category choices.

#Change or remove a value

Click a chip to highlight the step it comes from. To remove it, place the cursor beside the chip and press Backspace or Delete, then insert a different value if needed.

#Advanced: edit as text

Most workflows should use the picker. If you need to inspect or hand-edit the underlying text representation, select Edit as text below a field that contains a chip. This is useful for technical configurations such as custom API payloads; return to the visual view when you are done.