Reactivate automations (2.0) when unarchiving a project?

I found a temporary workaround to this! It’s a bit annoying, but looks to solve the issue for now.

I went into my automations and duplicated every one of them (I have 5). I then renamed them as a “Manual Trigger” and set the initial trigger (our main contact form, in our case) as a Manual Trigger instead.

I was then able to go into the newly unarchived project and add the manual trigger automations with the “Trigger Automation” option in the sub menu. Looks like that worked!

Still, it sure would be nice to be able to reactivate any/all cancelled automations within a project after unarchiving it!

It all depends on where you want them to be in the your workflow when they are unarchived. Are these people coming back ready to book and you’d be sending them down your booking workflow?

But one solution for you could be once unarchiving the project, you can put them into the appropriate pipeline stage which could automatically trigger an automation. You’d just need to have an automation that has the trigger of when a project gets moved to that stage. But you’d just want to make sure you want them to go through all the steps in that automation. That’s where the old builder was nice, you could edit a workflow’s steps before applying it- we can’t do that currently in the new builder

Exactly! With the old automations, we could do precisely that. I understand that the new automations work very differently, but it would still be nice if it could be arranged to simply reactivate what was already in place once a project is moved out of archive status.

Good tip about duplicating an automation and have it triggered by pipeline status, btw! :)

​@Joaquin Dedd It would be super nice to have the ability to edit the steps like in the old builder. And maybe that’s something they have in the works. I don’t even want to think about what all goes into building/coding a platform like HB- one thing that we think would be so simple to add could break so many other things on the backend. 

The new builder is just a completely different beast in how we think through how to build out our automations- our processes are still the same, but we have to build them so differently because of how the new builder operates. I think there’s a lot of good with the new builder, but it just takes a lot more brain power to make it work correctly. I say this as someone who’s business is literally setting up HB accounts for other people haha I feel everyone’s pain!

I’m glad that tip helped! Feel free to reach out with any other questions or issues you run in to (alyssa@graceandflowsystems.com). We can work through the 2.0 beast together! haha