Slack/Teams: Messages
Brian Holthouse avatar
Written by Brian Holthouse
Updated over a week ago

Hive Automate allows for a seamless integration with Slack and Teams using a set of automated workflows. We call these "recipes", and they can be highly customizable to fit specific business needs. They run by listening for a specific trigger in one of the systems, and then the recipe carries out a certain set of actions. Recipes can also be set to run on a specified schedule.

Lets take a look at the two Community Library recipes:

"When Action Card reaches specific status, send Slack message"


"When Action Card reaches specific status, send Teams message"

For each of these recipes you will need an active connection to either your Slack or Teams accounts set up in Hive Automate. You will also need the Workbot app added to either your Slack, or Teams channel.

In this recipe the trigger event is when an updated action in Hive is set to a specific status that is configured in Step 1.

Clicking into any open field within an action will give us a window with all the available datapills we can carry forward to different action steps in our recipe.

Now that we have information about this action card in Hive we can configure a message step in the recipe with all the information we want to provide. We can also gather more information about the user who created the action originally.

Here you will notice that we use datapills from multiple different steps to build out the desired message.

For 'Post message as Slack Workbot' this could look like:

Here you would specify first the channel to send the message, and then configure the content as either a message or notification.

For 'Post message to user as Workbot' this could look like:

You first have the opportunity to set a header block if you want, or multiple text blocks. Then you can configure the message below.

Datapills are great for passing dynamic variables into the message depending on what action card triggered the recipe. Here we use a datapill to pass the full name pulled from the user who created the card. We also pass the title of the card and the new status into the first line. Lastly we build a dynamic weblink for quick access to the card directly from the message in either of the other platforms.

Did this answer your question?