> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cassidyai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test with sample data

> Pull real records from a connected app to preview trigger fields and test your Workflow before the event actually happens.

Most [triggers](/workflows/building#trigger) only run when something happens in a connected app — a new HubSpot contact, a Slack message, a Google Sheets row. Waiting for one of those events to happen naturally makes it slow to test a Workflow, and you can't see what the real field values look like until it does.

**Test with sample data** solves this. It pulls a handful of recent, real records straight from the connected app so you can test your Workflow immediately — without publishing it and without waiting for a live event.

<Info>
  Sample data is available for most integration triggers (HubSpot, Salesforce,
  Slack, Google Sheets, and more) — see [supported
  triggers](#supported-triggers) below. It isn't available for the
  [Manual](/reference/triggers/manual),
  [Scheduled](/reference/triggers/scheduled),
  [Email](/reference/triggers/email), [Webhook](/integrations/webhooks), or
  [Meeting ended](/reference/triggers/meeting-ended) triggers, since those don't
  pull records from a connected app.
</Info>

## Load sample data

<Steps>
  <Step title="Open the Test Workflow panel">
    Open your Workflow, click **Edit**, then click **Test Workflow** in the editor toolbar.

    <Frame>
      <img src="https://mintcdn.com/cassidy/b8hgXRMme_1Tw3cX/images/workflows/test-workflow-panel.png?fit=max&auto=format&n=b8hgXRMme_1Tw3cX&q=85&s=655308c6e1868ca5e82edd8104af8b10" alt="Test Workflow panel showing the load sample data button" width="3822" height="1716" data-path="images/workflows/test-workflow-panel.png" />
    </Frame>
  </Step>

  <Step title="Click Test with sample data">
    If your trigger supports sample data, a **Test with sample data** row appears above the trigger inputs. Click it, or click **Load data**.

    If the row is disabled, connect the trigger's app first — a tooltip prompts you to connect your account.
  </Step>

  <Step title="Choose a recent event">
    A list of **Recent Events** from the connected app appears. Hover over any event to preview its field values, then click it to select it.

    <Frame>
      <img src="https://mintcdn.com/cassidy/b8hgXRMme_1Tw3cX/images/workflows/sample-data-popover.png?fit=max&auto=format&n=b8hgXRMme_1Tw3cX&q=85&s=a236e7487cc7f88f93fba9e71d9a578d" alt="The sample data popover with the list of recent events from the connected app" width="3822" height="1716" data-path="images/workflows/sample-data-popover.png" />
    </Frame>
  </Step>

  <Step title="Run your test">
    The selected record's values fill in the trigger inputs automatically. Click **Run Workflow** to test every downstream action against real data.
  </Step>
</Steps>

<Tip>
  Selecting an event doesn't run your Workflow by itself — it only fills in the
  trigger inputs. Review or edit the values before running if you want to test a
  specific scenario.
</Tip>

## Sample data respects your trigger's filters

If you've added filter conditions to your trigger — for example, a [HubSpot trigger](/integrations/hubspot/record-created-trigger) that only fires for deals in a specific stage, or a [Slack trigger](/integrations/slack/slack-message-trigger) scoped to one channel — sample data fetching applies those same filters. You'll only see records that would have actually triggered the Workflow, instead of scrolling through unrelated ones.

If no recent record matches your filters, the list shows **No records found**. Try loosening the filter temporarily, or pick a broader trigger event to confirm your Workflow logic before narrowing it back down.

## Discover field values before you build

Hovering over an event in the **Recent Events** list expands a preview of every field on that record, including nested objects and lists — the same fields available to reference in later actions. This makes it easy to find the exact field you need and see what its real API value looks like (a HubSpot lifecycle stage, a Slack user ID, a Google Sheets cell) before you go looking for it in the [variable picker](/workflows/building#variables).

## Supported triggers

Sample data is available for the following integration triggers:

| App                                                                                            | Trigger events                                                  |
| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| [Airtable](/integrations/airtable/workflows)                                                   | Record created, updated, deleted                                |
| [Box](/integrations/box/overview)                                                              | New file, new folder, file/folder events                        |
| [Gmail](/integrations/google-workspace/gmail/new-email-trigger)                                | New email                                                       |
| [Gong](/integrations/gong/new-call-transcript-trigger)                                         | New call transcript                                             |
| [Google Calendar](/integrations/google-workspace/google-calendar/new-or-updated-event-trigger) | New or updated event                                            |
| [Google Drive](/integrations/google-workspace/google-drive/workflows)                          | New/modified files, folders, comments                           |
| [Google Sheets](/integrations/google-workspace/google-sheets/workflows)                        | New row, new updates, new comment, new worksheet                |
| [HubSpot](/integrations/hubspot/overview)                                                      | Record created, updated (companies, contacts, deals, tickets)   |
| [Jira](/integrations/jira/overview)                                                            | New issue, updated issue, new event                             |
| [Monday.com](/integrations/monday/overview)                                                    | Item created, updated, deleted; subitem created; update created |
| [Outlook](/integrations/microsoft-365/outlook/new-email-trigger)                               | New email                                                       |
| [Outlook Calendar](/integrations/microsoft-365/outlook/new-calendar-event-trigger)             | New or updated event                                            |
| [Salesforce](/integrations/salesforce/overview)                                                | Record created, updated                                         |
| [SharePoint](/integrations/microsoft-365/sharepoint/workflows)                                 | New file, new folder                                            |
| [Slack](/integrations/slack/slack-message-trigger)                                             | New message, new reaction                                       |
| Smartsheet                                                                                     | New row, updated row, new comment, new attachment               |
| [Teams](/integrations/microsoft-365/teams/overview)                                            | New channel message, new chat message                           |
| [Zendesk](/integrations/zendesk/overview)                                                      | New ticket, updated ticket                                      |

<Note>
  Recently loaded events are cached for about a minute per trigger
  configuration. If you just created a new record in the connected app and don't
  see it yet, wait a moment and click **Load data** again.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Run and test a Workflow" icon="flask-vial" href="/workflows/running-and-testing">
    Learn about the full testing interface, including retesting individual steps
    and skipping actions.
  </Card>

  <Card title="Build a Workflow" icon="diagram-project" href="/workflows/building">
    Configure triggers, add filters, and reference data from other steps.
  </Card>

  <Card title="Share and deploy" icon="share-nodes" href="/workflows/sharing-and-deployment">
    Publish your Workflow once you've tested it with real data.
  </Card>
</CardGroup>