Ever find yourself building the same automation steps to solve different use cases, which results in slightly different flow solutions? So now you have clones of the same automation steps hanging out in multiple flows. And then, goodness forbid you have to make a change to those steps in all those flows? That can be a maintenance nightmare: first to find all the instances of those same steps, make the needed updates to the impacted flows, test those flows, and then move them through the deployment process. Sounds like potentially a LOT of work for very little value.
No one has time for all that. Life doesn’t need to be that complicated.
Did you know you can break off those repeated automation steps, make them into their own flow, and then reference that flow in all the different automations that use it?! Build it once, maintain it once, use it
Leave a Reply