Testing workflows

Testing workflows helps you confirm that your logic works before you connect it to your interface or publish your app.

What you can test

• Backend workflows (APIs): test server logic, access checks, and responses.
• Event triggers: test what happens when an event fires (for example “On magic link requested”).
• Interface workflows: test user actions by running your page in preview.

Test a single action

When you’re building a workflow, you can often test one action at a time.

This is useful when:

• You’re not sure which step is failing.
• You want to check the output of an action before you connect the next one.
• You want to confirm that bound values are correct.

How to do it

1. Open the workflow you want to test.
2. Select the action you want to test.
3. Run the test for that action.
4. Check the result in the debugger (see below).

Check results in the debugger

Use the Debug panel to confirm what happened during the test run:

• Logs: messages from actions like Log, and runtime errors.
• Variables: values that were used during the run (inputs) and values that were produced (outputs).

Common patterns for reliable tests

Start with fixed values

When you first test, use fixed values (not bindings) so it’s easier to see what works. Once the workflow is correct, replace fixed values with bindings from your UI.

Add temporary logs

Add a Log action before and after a step to confirm which data is going in and what comes out.

Test error paths

If your workflow uses Try/Catch, test both:

• A success case
• A failing case (for example, missing required data)

Common issues

The test succeeds but the app still doesn’t work

• Make sure the workflow is actually connected to the right trigger (button click, page load, etc.).
• If you’re using a view or API, make sure the access rules allow the current user to run it.

“Unauthorized” or “Forbidden” errors

• Check your API access checks (who can call the endpoint).
• Check the user’s roles and the role rules you applied.

Data looks different than expected

• Re-check which variables you bound.
• Confirm that your view parameters (if any) received the values you expected.