Skip to main content

​
What It Does

  • Automatically detects new emoji reactions on Slack messages so you never miss a customer or team response.
  • Triggers follow-up workflows—like notifications, logging, or CRM updates—without manual checks.
  • Provides visibility into engagement and sentiment across channels.
  • Keeps your dashboards and reports up to date with real-time reaction data.
  • Frees your team from polling Slack channels, reducing manual work and errors.

​
🏁 Getting Started

Slack Node config screenshot
1

Connect Slack

Choose your Slack workspace and authorize the app to read reactions.
2

Configure Inputs

Pick channels to monitor and set any filters or preferences.

​
Inputs

​
🛠️ Required Fields

None — this node only needs optional filters to start emitting events.

​
🎯 Optional Fields

  • Channels (⚪️)
    Select one or more channels to monitor for new reactions.
    Why it matters: Focus on the conversations that drive pipeline updates or customer engagement so you avoid noise.
  • Ignore Bots (⚪️)
    Toggle to skip reactions added by bot users.
    Why it matters: Keeps your workflows free of automated reactions and ensures only real user engagement triggers actions.
  • Icon (emoji) (⚪️)
    Filter by specific emoji names (e.g., thumbsup, fire).
    Why it matters: Track only key reactions—like approvals or alerts—to streamline your reporting and dashboards.
  • Include User Data (⚪️)
    Choose to include the full user object in the output.
    Why it matters: Get more context on who reacted for richer segmentation and deeper analytics.

​
Output

When a reaction is added, this trigger emits a structured event containing:
  • Message text and ID
  • Reacting user’s ID and info (if enabled)
  • Emoji name and timestamp
  • Channel or conversation ID
Slack Node output screenshot
If the same reaction is added multiple times, each event is emitted separately with its own timestamp.

​
How It Works

  1. Listens to your Slack workspace for any new emoji reactions on messages.
  2. Applies optional filters (channels, emoji types, bot ignore settings).
  3. Emits a clean, structured event with all reaction details.
  4. Triggers downstream workflows—like updating dashboards, sending alerts, or logging in your CRM.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
CSAT Alert”When someone reacts with :thumbsup:, send me a Slack DM.”
Deal Approval Tracker”Log a reaction of :white_check_mark: to our deal sheet.”
Team Engagement Dashboard”Track every :clap: across channels into a reporting sheet.”

​
✨ Pro Tips

  • Only monitor key channels to reduce noise—use the Channels filter.
  • Use @reaction and Insert Input buttons to pass emoji names into downstream steps.
  • If you need user details, enable Include User Data to enrich CRM updates.

​
⚠️ Important Considerations

  • Bot reactions can inflate event counts—enable Ignore Bots if you only want human feedback.
  • Large or high-volume channels may trigger many events—apply emoji filters to stay focused.
  • Ensure your Slack app’s permissions include reactions:read and channel access.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
No reaction events coming inApp not authorized or channel missingReconnect Slack or add the app to channel
Too many eventsNo emoji filter appliedAdd specific Icon (emoji) filters
Missing user detailsInclude User Data disabledToggle on the setting and re-run

​
📝 FAQ

Yes — just add each channel in the Channels field to monitor them all.
Use the Icon (emoji) filter to list the exact emoji names you care about.
This is a trigger node — it starts your workflow whenever a reaction is added.

​
💰 Pricing

ActionCredit Cost
Trigger Run (per event)1 credit
Trigger nodes that start workflows (like this one) cost 1 credit per event. All other action or enrichment nodes are free.

Capture every emoji reaction and seamlessly route it into your pipelines and dashboards — automatically. 🚀