Trigger Workflows When a Social Post Is Published

Casey and I built this both ways on the show, in about five minutes. She took the template the update points at and had the workflow in the portal: trigger on a social post property value change, broadcast status equals success, then the Slack notification. I pasted the update into Breeze Assistant in our portal and asked it to build the workflow for us. Breeze found the Slack notification action and a way to trigger on broadcast status changing to success, asked where the notifications should go, and published it. We got to the same place. So, will it breeze? Yes, it will.

Here is what I am getting at. You do not have to talk to me, but at least talk to Breeze. If you use ten percent of the energy you spend on email on social, you will see results. Any channel you are used to going to market with that is not working for you anymore, HubSpot has made it unbelievably easy to pick another channel and go, and now all you have to do is ask Breeze to help you figure it out. Social is on the table as an opportunity for every company, and it is going to be a central part of AEO moving forward. Email, I am pretty sure, is not.

Casey's first reaction when we first read this update was why do I need a workflow for this: alert the team to comment every time we post, and that will not get annoying at all. Ryan Ginsberg's suggestion was to send it to his dad. Fair, and it is why the notification is one step, not the strategy. Ryan's bigger point is that there are second, third and fourth steps after the notification, Breeze actions and agents that suggest replies and what to do next. Casey's build question was whether it has to fire for every social post, and it does not: filter it down to one show, or align it with the campaigns the posts belong to. She wants a Slack ping to the internal team when this show goes live, and she asked what other properties are on a social post; I had just asked Nectar the same thing, so keep an eye on custom properties for social posts. A social post, a task, a meeting: these newer triggers that are not object-based are a big part of the switch to the canvas, and as you add custom properties to social posts you can get as granular as the rest of your automation strategy. Just have a strategy, and if you share that strategy with Breeze it is going to help you execute it.

Who should act: Marketing Hub Professional and Enterprise teams that already post from HubSpot; opt into the public beta and start with the Slack template. Who can skip it: teams that do not publish social from HubSpot.