Get Reactions

slack.get_reactions
ActionChat & messagingconnection required

Calls the Slack Web API with the connection's bot token.

Read every emoji reaction on one message or file, with who added each.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Slack
Secret shape
the Slack bot token (xoxb-…), or {"token": "xoxb-…"}
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
channel
Channel id holding the message. Required together with timestamp.
stringNo———
timestamp
The ts of the message. Required once a channel is named.
stringYes—only with channel—
file
A Slack file id (F…) to read reactions on.
stringNo———
file_comment
A file comment id to read reactions on.
stringNo———
full
Return the complete user list per reaction rather than a truncated one.
booleanNofalse——
  • At least one of file, channel, file_comment must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "full": false
}

Output

One shape.

result

FieldTypeExample
type
What was read: message, file or file_comment.
string—
channel
The channel holding the item, when it is a message.
string—
reactions[].name
The emoji name, without colons.
string—
reactions[].count
How many people added that emoji.
number—
reactions[].users
The user ids that added that emoji.
array—
count
How many distinct emoji are on the item.
number—
{
  "channel": "",
  "count": 0,
  "reactions": [
    {
      "count": 0,
      "name": "",
      "users": []
    }
  ],
  "type": ""
}

Notes

  • The bot must be a member of a private channel before it can act there (Slack answers not_in_channel otherwise).
  • Slack rate-limits each Web API method on its own tier; a throttled call fails with the number of seconds to wait and is safe for the node's retry policy to repeat.

See Get Reactions run in a workflow.

In a technical demo we add the Slack connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.