How to test and troubleshoot your new workflows in Contractbook?
1. Test triggers:
Once you have set up your automation in the automation builder, you can begin testing your workflows.
Start by testing the triggers of your automations:
- For example, if a specific event triggers your workflow, make sure that the event is triggering the workflow as expected.
You can find a trigger testing section at the end of each automation workflow guide in our help center.
- For example, if the automation should start each time a form is completed, you can fill out the connected to your workflow form and check if this triggers an in-app automation under your account:
2. Check the activity log:
- To check the activity log for related automations, look for the three dots icon on the respective automation tab of the page.
- Click on the “activity” icon to open the activity log, which will show you a record of all recent actions taken by the automation.
Each step of a successfully executed automation will be actionable:
- You can click on the executed step, and this will lead you to the respective document, folder, task, or any other created by the workflow section under your account.
The activity log works great to fix issues with your automated workflow.
- This can help troubleshoot any issues or understand how the automation is functioning.
Activity logs on automations now show trigger data received:
This improvement makes it possible to troubleshoot any of your failed data entries.
Now, the automation owners can get all the insights directly from the activity logs review and use them to fix workflow errors.
- Read more about fixing failing automation here.
- To learn more about using the automations activity feed, you can read the article describing your specific workflow from this overview.
3. Check the output:
For native in-app automations:
- After testing the triggers and activity log of the respective automation, you should check the actions of your workflows.
- This could involve checking if the correct data is being entered into the correct data fields in the contract and if the correct email notification is being sent out (we recommend you use your own email with an alias to test the output before launching the workflow), or if the correct task is being created:
- You can test that by accessing each step of your executed automated workflow.
- You can find more guidance about testing the output of your in-app native workflows in our automation builder here.
For integrated in-app automations:
- If your workflow is based on the integration with another system, for example, your CRM system - then this step involves checking the properties you map in the automation builder are available in your CRM system.
- Any updates in external systems will influence the way your automations in Contractbook app work. Always ensure the correct data is linked when setting up these automated workflows.
- You can find more guidance about the in-app integrated workflows in our automation builder here.
By following these steps, you can ensure your workflows are thoroughly tested before launching.
This will help you to avoid any potential issues or errors that could impact your business processes.
4. Get help from us:
If you are still experiencing any difficulties or have questions, do not hesitate to contact our Support team.
Our experts are available to help you troubleshoot any issues and guide you on getting the most out of your automations.