Skip to main content

​
What It Does

  • Automate emoji reactions to signal approvals, feedback, or next steps.
  • Keep your team aligned by instantly marking messages with a reaction.
  • Reduce manual Slack clicks and streamline deal reviews.
  • Create visible markers for pipeline updates or campaign milestones.

​
🏁 Getting Started

Slack Node config screenshot
1

Select Account

Choose your connected Slack workspace where reactions will be added.
2

Configure Inputs

Pick the channel, message timestamp, and emoji to use as your reaction.

​
Inputs

​
🛠️ Required Fields

  • Select Account (✅)
    Choose the connected Slack workspace.
    Why it matters: Ensures reactions post in the right workspace and channel, keeping alerts and approvals in context.
  • Channel (✅)
    Pick the Slack channel where the target message lives.
    Why it matters: Directs your reaction to the correct conversation thread or project channel.
  • Message Timestamp (✅)
    Provide the timestamp of the exact message to react to (e.g., 1403051575.000407).
    Why it matters: Targets the specific message to mark status or feedback without confusion.
  • Icon (emoji) (✅)
    Select the emoji name (e.g., fire, thumbsup) to use as your reaction.
    Why it matters: Standardizes visual signals for approvals, priorities, or campaign highlights.

​
🎯 Optional Fields

None

​
Output

This action returns a confirmation payload containing details of the added reaction, including the channel, message timestamp, and emoji used. You can use this output to trigger follow-up steps—like logging approvals in a CRM or notifying stakeholders.
Slack Node output screenshot
The node will return an error if the message isn’t found or if it lacks permission to react.

​
How It Works

  1. Connects to your Slack workspace using the selected account.
  2. Locates the message by channel and timestamp.
  3. Adds the specified emoji as a reaction.
  4. Emits a confirmation payload to drive downstream workflow steps.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Deal Review Approval“Add :white_check_mark: when a deal moves to Contract stage.”
Campaign Highlights“React with :tada: on campaign kickoff announcements.”
Team Standup Status“Mark updates with :rocket: when key metrics hit goals.”

​
✨ Pro Tips

  • Use consistent emoji across workflows (e.g., :white_check_mark: for approvals) to keep signals clear.
  • Combine this action with a message fetch to react based on content keywords.
  • Use @Field inputs for dynamic reactions based on pipeline stage.

​
⚠️ Important Considerations

  • Ensure the connected account’s bot has access to the target channel.
  • Reactions can only be added to messages within channels where the bot is invited.
  • Incorrect timestamps will result in a “message_not_found” error.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Failing to add reactionBot not in channel or missing perm.Invite the bot to the channel and grant react scope.
Invalid timestamp errorTimestamp format incorrectCopy the exact message timestamp from Slack.
Reaction not visiblePermissions changed or message deletedVerify bot permissions and message status.

​
📝 FAQ

Yes — invite the bot to private channels to enable reactions.
Slack ignores duplicate reactions by the same user; only one will appear.
This is an action node, so it won’t cost any credits.

​
💰 Pricing

Action NodeCredit Cost
Add Emoji ReactionFree
All action nodes, like “Add Emoji Reaction,” are free. Only trigger nodes cost credits.

Drop this Slack action into your flow to automate message reactions and keep approvals visible — instantly. 🚀