# Test Trigger

Run a workflow manually from the editor with a custom payload.

The Test trigger runs your workflow from the editor with a payload you supply. It behaves the same as a real webhook trigger — steps are scheduled and run, credits are consumed, and live API calls execute. Use it to verify your workflow with controlled input before enabling it on live traffic.

## Running a test

1. Open the workflow editor.
2. Click **More actions → Test data** to open the editable **Request body** and **Request headers** panels. The request body becomes the `data` argument to `start`; the headers become the `headers` argument.
3. For Shopify webhook triggers, the request body is pre-filled with the topic's sample payload. You can view the sample at any time (read-only) via **More actions → Sample payload**.
4. Click **More actions → Run test**.

The workflow runs from `start` exactly as it would on a live trigger. A **Live Output** panel opens below the editor and listens for real-time step events. Each row in the table represents one step execution:

| Column | Description |
| --- | --- |
| Status | Green tick for success, red for failure |
| Status code | HTTP response code from the step dispatcher |
| Time | When the step executed |
| Duration | Wall-clock time for that step |
| Step | The method name that ran (`-` for the initial trigger) |
| Retries | How many times this step was retried |
| Data id | Internal identifier for this step's payload |
| Payload size | Size of the payload passed to this step |
| Task | Workflow name |
| Method | HTTP method used to dispatch the step |

> Caution: Test runs execute real API calls — `fetch()` calls hit live endpoints and credits are consumed. Use test order IDs or sandbox credentials if you want to avoid side-effects.