Summary
The branching step and wait step type in Automations help you create more flexible processes, with different actions based on conditions, and ensuring actions happen at the right time
The branching step is only available in Automations in upgraded Planhat (ws.planhat.com), in our flowchart UI
Who is this article for?
Planhat users who will be configuring Automations for their team, e.g. CS Ops
Branching
Branching enables you to have one trigger, with multiple outcomes.
You can use branching in Automations to execute different steps based on conditional logic. This is extremely powerful, as you can create different processes with one single trigger, reducing the number of Automations you need to create. An example is deal routing, to automatically assign incoming deals based on ARR and region, ensuring the right sales team takes action.
How it works
You can create multiple branches in a single Automation. If multiple conditions match, all relevant branches will run. The conditions can reference any model/record used in the Automation, and conditions and steps can be renamed to ensure a clear and easy-to-follow sequence of steps.
📌 Important to note
To create a branch condition, define the conditions rules by typing << and finding the field to condition on in the dropdown. If you're unsure of what the field name is, check the "Fields" tab of the "Data" Global Tool.
Examples
To reference the Health of a Company (where company is the trigger), write <<object.h>>
To reference the ARR of an Opportunity (where opportunity is the trigger), write <<object.arr>>
To reference the Phase of a Company (where Company is accessed through a GET step with name "Step X"), write <<Step X.phase>>
Click the image to view it enlarged
📌 Important to note
When creating conditions for branches, make sure to select the correct field type for correct comparison. As an example, the ARR field on Opportunity is a number field. With an appropriate field type, comparisons such as "more than" or "less than" can be used.
Wait
"Wait" enables you to control when actions happen.
You can time your processes perfectly using delays in Automations. The wait step lets you pause an Automation for a specific amount of time before the next step runs.
Wait for minutes, hours, or days (up to 30 days).
Set the Automation to continue on a specific future date (within 30 days).
Click the image to view it enlarged
📌 Important to note
If an Automation with a wait step is updated the existing Automations will still execute the planned steps. If an Automation is deleted, the steps will be cancelled.