As you get started with Automations 2.0, you may want to try out an automation before activating it. HoneyBook makes this easy with a built-in test run feature. Running a test helps you see exactly how your automation will behave before setting it live.
Why Use a Test Run?
When you use a test run:
HoneyBook creates a dedicated project to run the test, keeping all test activity separate from your live workflows.
You can preview automation behavior to understand how each action will fire.
You can skip waits and conditions to move quickly through the sequence.
You can see actions unfold in real time, removing uncertainty before activating your automation.
🚦Before you begin:
Test runs are only available in Automations 2.0.
Automations that integrate with third-party apps cannot be tested using this method.
HoneyBook will create a new project during the test—the project will be used only for testing.
How to Start a Test Run
📚 Note:
You can only test automations that aren’t activated yet.
To start testing your automation:
From the navigation menu, go to Automations > All
Click into the automation you want to test.
In the top right corner, click Test Run > Start Test
At this point, HoneyBook will run the automation, creating a test project and client in your account. If you want to skip waits or conditions, click Skip next to the step in the right-hand panel.
If necessary, follow any other on-screen prompts.
Next Steps
Review your test project to confirm your automation ran successfully.
Example: If you set up an automation that creates a task after a client’s first payment, make sure that task appears in the project.
Clean up your test project once you’ve confirmed everything worked as expected.
⚠️ Important: Test projects are not automatically removed. You’ll need to manually delete or archive the test project yourself. This step keeps your pipeline and reports clean.
Still have questions? Feel free to send us a message by clicking the Question Mark icon on any HoneyBook page. Our team is always happy to help!