Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors
22.5k Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

Send to Slack

Use this node to post a message to a Slack channel or user — for example, notifying a DevOps channel when a server device goes offline, or sending a direct message to an on-call engineer when a critical alarm fires.

  • Message template — required. Content of the Slack message. Supports templatization — use ${metadataKey} and $[dataKey] to include dynamic values.
  • Use system Slack settings — when enabled, uses the Slack bot token configured at the system level. When disabled, specify the Bot token directly in this node.
  • Bot token — Slack API bot token (required when system settings are disabled).
  • Conversation type — PUBLIC_CHANNEL, PRIVATE_CHANNEL, or DIRECT.
  • Conversation — target Slack channel or user (identified by Slack ID/name).
  1. Resolve the message content from the template using incoming message data and metadata.
  2. Post the message to the configured Slack conversation via the Slack API.
  3. Route via Success on delivery. Message data and metadata are not modified.
  4. Route via Failure on unexpected error.
Connection Condition
Success Message posted to Slack successfully.
Failure Invalid token, Slack API error, or unexpected error.

Example 1 — Post device alert to a channel

Section titled “Example 1 — Post device alert to a channel”

Metadata: { "deviceName": "Gateway-01", "alarmType": "Connection Lost" }.

{
"messageTemplate": "Alert: ${alarmType} on device ${deviceName}",
"useSystemSettings": true,
"conversationType": "PUBLIC_CHANNEL",
"conversation": { "id": "C12345678", "name": "alerts", "type": "PUBLIC_CHANNEL" }
}

Result: "Alert: Connection Lost on device Gateway-01" posted to the #alerts channel. Routes via Success.

{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "TbSendToSlackNodeConfiguration",
"type": "object",
"required": ["messageTemplate"],
"additionalProperties": false,
"properties": {
"messageTemplate": { "type": "string" },
"useSystemSettings": { "type": "boolean" },
"botToken": { "type": "string" },
"conversationType": { "type": "string", "enum": ["PUBLIC_CHANNEL", "PRIVATE_CHANNEL", "DIRECT"] },
"conversation": { "type": "object" }
}
}