Skip to main content

Send Slack messages with App Workflows

Use native Hive Workflows to message Slack channels, specific people, action assignees, or dependent action assignees.

Written by Ellen Kajca

Use Hive’s Workflows app to send Slack messages automatically when work changes. Start here for new Slack automations: you can send to a channel, specific people, the triggering action’s assignees, or the assignees of dependent actions, without building a Hive Automate recipe.

Before you start

  • Post to Slack requires a paid plan.

  • Connect Slack to Hive. Open Apps, find Slack, and follow the connection flow. See Hive for Slack for installation instructions.

  • The workflow uses its owner’s Slack connection. Make sure that connection can send to your intended destination.

  • Use a workflow that runs on a Hive action, such as an action status change. This Slack operation needs an action to send its message.

Create your Slack workflow

  1. Open Workflows from the sidebar or Apps. Select Create workflow, then Build manually.

  2. Choose your When trigger and configure the relevant project and conditions. For example, choose a status-change trigger for actions that become Blocked.

  3. Add Post to Slack as a Then operation.

  4. Under Send to, choose a recipient option from the list below.

  5. Write your Message. Use message tokens to include details such as Action title, Status, and Action URL. Use Insert custom field to add an action custom field.

  6. Review the sending options. When ready, set the workflow to Enabled and select Save workflow.

  7. Trigger it with a test action. Check both the workflow’s View runs history and the message received in Slack.

You can also use Create with Buzz to describe the automation, then review the generated trigger, recipients, and message before enabling it. See Workflows overview.

Choose who receives the message

  • Slack channel or DM: Select a fixed destination from Select channel or DM. Each run sends to that destination.

  • Specific people: Choose Hive workspace members under People. Hive matches them to Slack accounts and sends each person a direct message.

  • Triggering action assignees: Send direct messages to the assignees of the action being processed. Recipients change with the action, so you do not need to maintain a fixed list.

  • Dependent action assignees: Send direct messages to assignees of the action’s linked successor actions—the actions that depend on it. This is useful for handoffs. The lookup considers up to 10 linked successor actions.

People must belong to the Hive workspace and have a matching Slack account. People without a match are skipped. If one person is assigned to several dependent actions, they receive one message per Slack operation.

Example: notify assignees when an action is blocked

Choose a trigger for an action’s status changing to Blocked. Add Post to Slack, set Send to to Triggering action assignees, and write a message using the Action title and Action URL tokens. Each run sends the message to the relevant assignees.

Sending and formatting options

  • Send with workspace Slack bot: Select this to send using the bot connection associated with the workflow owner’s Slack integration. With it cleared, the workflow uses the owner’s personal Slack connection. Choosing a channel normally selects the bot option; choosing a DM or people-based recipient mode normally clears it. Review this setting before saving.

  • Comment on action if Slack send fails: Select this to add a comment to the action when a Slack send fails. Skipping a person without a matching Slack account does not count as a send failure.

  • Block Kit JSON (optional): For advanced formatting, enter a valid JSON array of Slack blocks. Keep a non-empty Message as well; blocks do not replace that required field.

Successor message tokens describe the first dependent action. They do not create a separate, personalized message for each dependent action’s assignee.

If a message does not arrive

  • Confirm the workflow is enabled, the trigger matches, and the run has a Hive action to process.

  • Check the workflow owner’s Slack connection and whether the selected personal or bot connection can send to the destination.

  • For people-based recipients, check workspace membership, action assignments, and matching Slack accounts. For dependent recipients, check the action’s successor links and their assignees.

  • Open View runs to inspect failures. A people-based operation can show Completed even when no recipients could be matched, so also confirm delivery in Slack.

Already using Hive Automate?

For new Slack automations, start with the native Workflows app and the steps above. If you are maintaining an existing Hive Automate recipe, its separate instructions remain available in Slack/Teams messages with Hive Automate. That guide covers recipe and Workbot setup; this guide covers native App Workflows.

Did this answer your question?