HoneyBook Automations 2.0 Feature Requests

Yes!!! Why was the project date removed at all?

agreed! so frustrating

You are able to set the project date as a trigger and have it begin before a project date - does this help your use case? Let us know! 

An additional update request is to be able to edit an email that is triggered to send which requires approval.  There is no way to edit this email before sending and that is frustrating. 

Hey ​@Federico! You can upvote the feature request for that here :) 

Agree I loved being able to set different tasks to be done so many days or weeks before the project date. Not just the trigger starting point. 

You are able to set the project date as a trigger and have it begin before a project date - does this help your use case? Let us know! 

It could… however, it makes the workflow very messy to have to create a new automation every time I need one done based on project date.

I would love to be able to skip a task in Automations 2.0, like we are able to in the Old Automations. There are times I forget, and want to just skip the step and have it continue to go down the automation line. 

This is what is missing from automations 2.0

I need to send a questionnaire 32 days before project date and I REALLY want to keep this inside my active automation and not create a new one.

Any updates on when this will be possible? I really don’t understand why this trigger was removed?

Agreed! The new updates are great, but the functionality actually makes it much more difficult to work through these automations vs the old automations fully with my clients.

Not having the ability to edit file templates, skip steps, start from a specific step, or even “fast forward” through wait times for clients who may have a quicker timeline than others is extremely frustrating. Constantly having to duplicate an automation to make small edits is not ideal when you’re trying to make things as efficient as possible.

I hope the Honeybook team really hears the community on this topic and makes the suggested changes in automations 2.0 because it would really make a world of a difference in keeping the automations as simple and efficient as possible for business owners.

I am so grateful that I came in here before I started building all my automations in 2.0. All of these concerns are valid, and have now caused me to rethink converting to 2.0.  

I have to admit I was pretty excited to finally have the time to do it as it closely follows Go High Levels workflows, which I am great at building, and there too I can not edit the emails that clients get which what I use it for hasn’t been an issue. But in Honeybook, this would be an issue as occasionally I do need to skip part of an automation, or edit and email that they will receive for what ever reason.

Losing this functionality along with not being able to move them to the next part of their automation if they pay their invoice in full with a bank account is annoying. “ACH bank transfer payments, this step will only proceed once the transfer has been fully processed, not when it is initiated” This means that if a client signs their contract and pays their invoice in their smart file they will not get my “ Yay, you are booked” email. Yes, I know I can trigger it to send after they sign, however a signature and payment are needed to secure their booking. I tried to solve this by putting the invoice 1st, yet the too gets an oops message that the contract needs to be before the invoice.

I have waited a year for kinks to be worked out.  Seem I need to continue to wait. I love HoneyBook, but the new updates are not quite up to where my business needs them to be.  But I do love the Conditional waits! Thank you for those. 

Hi ​@Shae Gines,

1. You can skip steps in Automations 2.0!
2. You can edit emails in the automation. This is called an “Email Draft” action, so it will pop up at the right time, but you can edit and approve it before sending it.
3. Just like you mentioned, I would recommend using the contract condition. You can always make a task after the contract is signed to ensure you’ve received the payment before the automation sends the “Yay, you’re booked” email. But I know that still feels a bit clunky