# Using Data Across Steps Getting data from one step to another is essential for building workflows. In fact, most workflow logic involves passing data between steps. Whether you're passing an email address from a form to a new email, using AI output to update a spreadsheet, or accessing nested CRM data, understanding Step Outputs is key to building effective automations. ## What Are Step Outputs? **Step Outputs** are the reusable data created by triggers and steps in your workflow. They appear as "pills" like Step output pill showing step number 1, Gmail logo, and Contact type that you can reference in later steps. Each pill shows: * The **step number** that created it (step #1 is always the Trigger) * The **app logo** where the data comes from (e.g., Gmail, HubSpot) * The **data type** (e.g., Email, Row, Contact)
Relay.app workflow editor showing step output pills connected to their originating steps with visual lines

Step Output pills help you understand where data came from

*** ## The Basics ### How Data Enters Your Workflow Step Outputs are created in four main ways: 1. **From** [**Triggers**](https://docs.relay.app/triggers/triggers-101) - e.g., email addresses, subjects, attachments from an "email received" trigger 2. **From** [**Find Steps**](https://docs.relay.app/data/find-steps) - e.g., CRM contacts matching a company name 3. **From** [**Actions**](https://docs.relay.app/actions-in-apps/actions-101) - e.g., a newly created Google Sheets row 4. **From** [**AI Steps**](https://docs.relay.app/ai/ai-steps) - e.g., extracted invoice amounts, dates, and vendor names ### Understanding Data Types Every field in a Step Output has a specific **type** (Text, Date, Number, URL, Email, File, or app-specific types like Contact or Subscription). **Why types matter:** Relay.app uses types to ensure data flows correctly between steps. For example, a Gmail attachment field only accepts File types, and a "Scrape text from website" step expects a URL type.
Gmail send email step showing attachment field that only accepts File type data from compatible step outputs

Type-safe inputs help prevent configuration errors

### Always Up-to-Date Data {% hint style="success" %} **A powerful feature:** Step Outputs automatically fetch current data from the source app every time they're used—even if the underlying data changed after the trigger fired. **Example:** If a calendar event's start time changes during a workflow with a "wait 5 days" step, referencing that start time later will show the updated value. **Benefits:** * No need to re-fetch data with Find steps * Works seamlessly with [Wait steps](https://docs.relay.app/flow-control/wait-steps) * Always reflects the current state of your data {% endhint %} *** ## Using Step Outputs in Your Workflow ### Three Ways to Insert Data You can reference Step Outputs in subsequent steps using any of these methods: 1. **Text inputs - \[+] button**: Best for exploring available data and browsing all options 2. **Text inputs - @ shortcut**: Fastest method when you know what you're looking for 3. **Typed inputs**: Use the type-specific picker (e.g., date picker, contact picker) for automatic type safety
Text input field with data picker menu opened showing available step outputs and data fields to insert

Inserting data via the [+] menu

Text input field showing @ symbol autocomplete menu with step output suggestions for quick data insertion

Quick insert using '@' keyboard shortcut

Date picker interface showing available date-type step outputs for selection in a typed input field

Type-specific picker for dates

### Accessing Specific Fields When you need a specific field from a Step Output, it appears in the pill: Step output pill showing Gmail Contact with First name field specified ### Working with Nested Data Step Outputs provide instant access to linked data at any depth—no extra lookup steps needed. Nested levels are shown with a `>` symbol, like this: Step output pill showing Paddle Subscription > Customer > Email address with nested hierarchy **Real-world example:** In a sales workflow triggered by a new deal in HubSpot, you can directly access: * **Deal > Associated Contact > Email address** - to send a personalized email * **Deal > Associated Company > Industry** - to route to the right team * **Deal > Owner > Name** - to notify the account manager All without adding separate "Find Contact," "Find Company," or "Find User" steps.
Data picker showing hierarchical access to nested objects with Contact > Company > Deal structure demonstrating linked data access

Navigate infinite levels of linked data effortlessly

*** ## Troubleshooting ### Common Issue: Can't Find the Data I Need **Problem:** You want to use data from a previous step, but it doesn't appear in the picker. **Example:** You have a Slack message containing a URL, and you want to scrape it. But when you try to select the URL in the "Scrape text from website" step, nothing appears. **Why this happens:** Relay.app enforces type matching for safety. The Slack message body is Text type, but the scraping step expects a URL type. **Solution:** Use an AI step or data transformation to extract the URL from the text first. Once you have a proper URL type, it will appear in the picker. ### Inspecting Available Data To see all fields available in a Step Output: 1. Open the step configuration dialog that created the output 2. Look at the **Output** section at the bottom 3. Click the Step Output pill to explore its structure
Animated demonstration of clicking on a step output pill in the step configuration dialog to view available data fields and structure

Inspect Step Output structure by clicking its pill

## Next Steps **Ready to build more complex workflows?** * [**Find Steps**](https://docs.relay.app/data/find-steps) - Search for specific data in your connected apps * [**Lists and Arrays**](https://docs.relay.app/data/lists-arrays) - Handle multiple items at once with loops and filters * [**Transform Data**](https://docs.relay.app/built-in-actions/transform-data) - Convert between data formats and manipulate values * [**Inspecting Run Data**](https://docs.relay.app/data/inspecting-run-data) - Debug workflows by examining actual data from runs