Test Your Workflow Right Inside AI Builder
AI Builder now tests what it builds. Describe a workflow, let AI Builder build it, then click Test workflow in the same chat. The test runs for real, every step reports back on the canvas, and AI Builder tells you in pl…
AI Builder now tests what it builds. Describe a workflow, let AI Builder build it, then click Test workflow in the same chat. The test runs for real, every step reports back on the canvas, and AI Builder tells you in plain words what worked.
Test workflow, right in the chat
- Every time AI Builder builds or edits your workflow, its reply ends with a Test workflow button.
- Click it and the test opens inside the chat. Choose Enroll a contact or Test using events, pick the contact, and check the contact data before you start.
Watch the run live
- Click Start test run. The canvas shows each step as Running, then Success, Action skipped or End.
- The chat lists the run step by step, with a check next to every step that ran.
A summary you can read
- When the run ends, AI Builder writes a short test summary: which steps ran, which were skipped, and whether there were errors or missing data.
- Click any step on the canvas to see its Input and Output from the run.
Run another test
- Changed something? Click Run another test to test again with one click.
- Open Secure Automation Labs and turn on The New Test Workflow.
- Go to Automation > Workflows and open a workflow.
- Open AI Builder and describe the workflow you want, or the change you want.
- When AI Builder finishes, click Test workflow in its reply.
- Choose Enroll a contact and pick a contact, or choose Test using events.
- Click Start test run.
- Read the test summary. Click any step on the canvas to see its Input and Output.
- Save and publish your workflow.
Important: A test runs the real steps. Tags are added, notes are written, and messages are sent. Test with your own contact when you do not want to reach a customer.
Why This MattersBuilding with AI is fast. Knowing it works used to be the slow part. You had to leave the chat, find the test, and dig through logs to see what happened.
Now build and test live in one place. Describe it, build it, test it, read the result. No guessing, no digging through Execution Logs, no hoping it works in production.
Good to Know- Some actions are skipped in a test run. The summary and the canvas tell you which ones.
- Testing is optional. You can save and publish without testing.