Integration: Send Message on Slack
The Send Slack Message node allows your workflow to send automatic messages directly to channels or users in your Slack workspace. With it, you can notify teams about new records, alert responsible parties about pending approvals, communicate process results, and more — all without manual intervention.
Unlike nodes such as Approval or Request Form Response, the Slack node advances immediately after sending the message, without waiting for recipient interaction.
Prerequisite: Configure Slack Connection
To use this node, you need to have a Slack connection configured in your Space. The connection is made via OAuth, which means you authorize Hashdata to send messages on behalf of your workspace securely.
There are two ways to create the connection:
-
Through the Integrations menu: Go to Settings → Integrations → click New connection → select Slack. A Slack authorization window will be displayed. Log in to your Slack account, choose the workspace, and click Allow. The connection will be saved and will be available for all workflows in the Space.
-
Directly in the node panel: When configuring the Send Slack Message node in the workflow editor, click the Connection field and select the option Create new connection. The OAuth authorization popup will open without you needing to leave the workflow. After authorizing, the connection is automatically saved in the Space and is already selected in the node.
During connection creation, you will need to authorize the Hashdata app in your Slack workspace. This authorization is done once per workspace. Only Slack workspace administrators or users with permission to install apps can complete this step. If you don't have this permission, contact your Slack administrator to request approval.
Configuration
After adding the Send Slack Message node to the canvas, click on it to open the configuration panel. Fill in the fields as described below.
| Field | Description | Required |
|---|---|---|
| Connection | Select the Slack connection previously configured in the Space. If there is none yet, use the Create new connection option to authorize now. | Yes |
| Recipient type | Choose between Channel (sends the message in a public or private workspace channel) or Direct user (sends as a direct message — DM — to a specific user). | Yes |
| Channel / User | Select the destination channel or user from the list automatically loaded from your Slack account. The list is populated based on the selected connection. | Yes |
| Message title | Short text displayed as the message header or highlight in Slack. Ideal for quickly identifying the subject, for example: New purchase request received. | Yes |
| Message content | Body of the message sent. Supports free text and workflow variables in the format {{field_name}} to include dynamic data, such as requester name, approved value, date, among others. | Yes |
| Action buttons (optional) | Currently, the only action button is "Edit response", which will open the response for editing. | No |
Use variables in the format {{field_name}} in the title and message content to make them dynamic and relevant for each workflow instance. For example, if your form has a field called requester_name, you can write: New request received from {{requester_name}}. Available variables are all responses collected in previous forms in the same workflow.
Node Outputs
The Send Slack Message node has two possible outputs on the canvas, allowing you to handle success and error situations independently:
Success
The Success output is triggered when the message is successfully sent to Slack. This occurs when the connection is active, the recipient (channel or user) is valid, and the Hashdata app has the necessary permissions in the workspace.
From this output, you can connect any other node to continue the flow — for example, a Set Status node to record that the notification was sent, or an Approval node to wait for a decision.
Error
The Error output is triggered when the message send fails for any reason, such as:
- The Slack connection was revoked or expired
- The selected channel was deleted or the bot was removed
- The destination user no longer exists in the workspace
- Temporary connectivity issues with the Slack API
By handling the Error output, you can, for example, send an email notification to the workflow administrator, set a failure status on the instance, or try an alternative route.
If a Slack workspace administrator revokes the Hashdata app permissions, all future executions that use that connection will follow the Error output. To resolve, go to Settings → Integrations, remove the problematic connection, and create a new authorized connection.
Usage Examples
New request notification
A workflow with a form trigger can use this node to automatically notify the #requests channel whenever a new response is submitted. The message content can include the requester's name, the type of request, and a link to view the complete response.
Pending approval alert
After an Approval node is created, you can add a Send Slack Message node before it to notify approvers via Slack — as a complement to the email — that there is an approval awaiting their action.
Export confirmation
In workflows that export data to spreadsheets or make calls to external systems, use this node at the end of the flow to notify the responsible channel that the process was completed successfully.
Tips and Best Practices
- Prefer channels over direct users for team notifications, as channels allow multiple members to follow the process without depending on a single person.
- Use action buttons when you want to capture a quick decision in Slack without requiring the user to access the Hashdata platform.
- Manage connections centrally: the same Slack connection can be reused in multiple Space workflows, without needing to re-authorize.
- Test the node before publishing the workflow, using the editor's test execution function, to ensure the message arrives correctly at the expected destination.