Test Scope. Run Live Workflows for Just One User

Testing a workflow has always been a trade off. The "Send Test" button fires everything instantly, skips waits, skips conditions, and sends to your inbox. It tells you the emails look right, but it doesn't tell you whether the workflow actually behaves correctly in the real world. Delays fire at the right time? Conditions evaluate properly against live event data? You'd only find out when real users start hitting it.

Test Scope changes that. You can now scope any live workflow to a single user. The workflow stays active, processes real events, respects real delays and conditions, but only triggers for the user you specify. Everyone else is ignored until you remove the scope.

How it works

Open any workflow and click the Test Scope button in the actions bar. Enter an email address and save. That's it.

The workflow is still marked as Active. Events still flow in. But when the worker picks up an event and matches it to your workflow, it checks the scope. If the event came from a different user, it skips silently. If it matches your scoped user, it runs the full workflow: delays, conditions, emails, webhooks, all of it.

Real conditions, real timing

This is the part that matters most. When you use Send Test, conditions are bypassed entirely. A "check if user opened the email within 24 hours" step just gets skipped. With Test Scope, that condition actually runs. The worker waits, checks for the event, and branches accordingly. You see exactly what a real user would experience.

Same with delays. A 24 hour wait is a real 24 hour wait. If your workflow has a "wait 1 hour then check if they visited the pricing page" flow, scoping to yourself lets you trigger the event, go about your day, and come back to verify the email arrived on schedule.

Visible everywhere

When a workflow is scoped, you'll see it. On the detail page, the Test Scope button turns orange and shows the scoped email address. On the workflow list page, an orange "Test Scope" badge appears next to the status badge so you never forget one is still scoped.

This is intentional. A scoped workflow is effectively invisible to all your other users. That's great for testing, but you don't want to accidentally leave it running like that for weeks. The visual cues are there to remind you.

Clearing the scope

When you're done testing, click the Test Scope button again and hit Clear. The workflow immediately starts processing events for all users. No restart needed, no toggling it off and on.

When to use it

Test Scope is designed for the gap between "Send Test" and "ship it to everyone." Some examples.

You've built a new onboarding flow and want to walk through it yourself. Set the trigger to $identify, scope it to your email, create an account with that email in your app, and watch the whole sequence play out over the next few days.

You've tweaked the timing on an existing workflow and want to verify the delays work before it affects paying customers. Scope it, trigger the event, and observe.

You've added property filters to a condition and need to confirm they match correctly against real event data. Scope it, fire events with the right properties, and check whether the workflow branches as expected.

Available now

Test Scope works on all plans. Open any workflow, click Test Scope, and start testing in production without the risk.

Open your workflows and try it.