# Test a saved workflow

## Before you start

An owner or admin can run a test. A matching test sends a **real webhook** to the selected connection, even without publishing. Use a receiver appropriate for that action.

## Steps

1. Open **Workflows** at `/workflows`. Save or discard edits before testing.
2. Use the supported four-node path: visitor identified → lead rule; Match → webhook, No match → end.
3. Select an enabled saved lead rule and an enabled saved webhook connection.
4. Open **Test this workflow**, enter sample visitor facts, and submit the test.
5. Read its status and node outcomes. Use **Check test status** if needed. The test continues if you leave the page.

## Understand the result

A succeeded test means the receiver acknowledged the webhook. It does not prove the receiver completed downstream work and does not publish the workflow. No match means no webhook was sent. Pending or unconfirmed states are not success. Results belong to the displayed saved version; later edits do not change that result.

## If testing is unavailable

Read the readiness message. Check your role, unsaved edits, node connections, enabled rule and enabled webhook. Do not assume that an arbitrary draft graph is executable. This guide does not claim that publishing is supported for every graph or enabled in production.

Test a saved workflow

Before you start

An owner or admin can run a test. A matching test sends a real webhook to the selected connection, even without publishing. Use a receiver appropriate for that action.

Steps

Open Workflows at /workflows. Save or discard edits before testing.
Use the supported four-node path: visitor identified → lead rule; Match → webhook, No match → end.
Select an enabled saved lead rule and an enabled saved webhook connection.
Open Test this workflow, enter sample visitor facts, and submit the test.
Read its status and node outcomes. Use Check test status if needed. The test continues if you leave the page.

Understand the result

A succeeded test means the receiver acknowledged the webhook. It does not prove the receiver completed downstream work and does not publish the workflow. No match means no webhook was sent. Pending or unconfirmed states are not success. Results belong to the displayed saved version; later edits do not change that result.

If testing is unavailable

Read the readiness message. Check your role, unsaved edits, node connections, enabled rule and enabled webhook. Do not assume that an arbitrary draft graph is executable. This guide does not claim that publishing is supported for every graph or enabled in production.