I just had a set-up service with a client who is on a different version of HoneyBook. They do not have the ability to add automations to projects but automations can only be triggered within ‘universal automations’ that have been set-up. With this new feature HoneyBook is testing, you can’t manually add automations to projects, it will be dependent on a trigger. IDK if anyone else has seen this new feature.
Biggest differences from our automations builder today:
- You do not need to (and can't) manually apply an automation,
- as long as the trigger happens in a project, the active automation will start running
- Because you aren't applying to a project anymore and instead the automations are just triggering on their own, you can have multiple automations happening inside of any given project
- The new "Condition" step in the automation flow introduces branching logic based on specific criteria. When the flow reaches this step, it checks whether certain conditions have been met.
These conditions are related to previously configured steps where smart files were sent or tasks were created, or if a session was scheduled. The "Condition" step then branches into two paths: "Yes" (true) and "No" (false). - You can also set a timeframe for the condition to be evaluated. If the condition is met within this timeframe, the flow proceeds along the "Yes" path; if not, it continues along the "No" path after the timeframe ends.
I like the conditional option in the new feature, but being able to manually add an automation to a project, not dependent on a specific trigger, was a big feature I enjoy.
