Hive Automate allows for a seamless integration with Email 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 Community Library recipe:

"When Action Card reaches specific status, send an Email".

For this recipe you will need an active connection to your Gmail or Outlook based email. Other email domains can be accommodated through a generic email connector as well.

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 an email 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 email recipient, subject, and message.

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 email pulled from the user who created the card. We pass the title of the card and the new status into the subject line. Lastly we create an email body that provides details, and builds a dynamic weblink for quick access to the card directly from the email.

Email messages can also be configured in Text, or HTML email types.

This community library recipe already has both the Gmail and Outlook connections set up for ease of use. Feel free to chose which one you need and delete the other.

Did this answer your question?