Skip to main content

What It Does

  • Monitors one or more Slack channels for a specific keyword.
  • Fires an event the instant the keyword is mentioned, so you never miss critical flags.
  • Helps SalesOps and GTM teams auto-notify or update dashboards when deals or campaigns hit key terms.
  • Cuts down manual checks—keep your pipeline alerts and team dashboards in sync without lifting a finger.

🏁 Getting Started

Slack Node config screenshot
1

Authorize Slack App

Connect and authorize your Slack workspace so the node can listen to messages.
2

Configure Inputs

Pick channels, set your keyword, and decide if bot messages should be ignored.

Inputs

🛠️ Required Fields

  • Slack Apphook (✅)
    The webhook interface that lets this node receive Slack events.
    Why it matters: Without it, the node can’t listen for your keywords.
  • Keyword (✅)
    The exact word or phrase you want to track in your channels.
    Why it matters: Pinpoints the trigger—only events matching your term will fire downstream actions.

🎯 Optional Fields

  • Channels (⚪️)
    Select one or more Slack channels to monitor.
    Why it matters: Narrow down noise—focus on relevant team or campaign channels.
  • Ignore Bots (⚪️)
    Toggle to skip messages sent by bots.
    Why it matters: Keeps your workflow free from automated chatter and test messages.

Output

The node emits a structured event whenever your keyword appears. Each event includes:
  • message text
  • user ID and name
  • channel ID and name
  • timestamp of the mention
This payload can drive downstream steps like notifications, CRM updates, or data enrichment.
Slack Node output screenshot
If the same keyword fires simultaneously in multiple channels, each mention emits a separate event.

How It Works

  1. Your Slack Apphook subscribes to message events in selected channels.
  2. The node scans incoming messages for the exact keyword.
  3. When a match occurs, it builds a payload with message and user details.
  4. Downstream actions—like alerts, dashboards, or CRM updates—trigger automatically.

🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Urgent Deal Alerts”Fire when ‘🚨Urgent Deal’ is mentioned in #sales-alerts.”
Campaign Mentions Tracker”Notify Ops when ‘Black Friday’ appears in #marketing-updates.”
Deal Hygiene Check”Trigger workflow on ‘missing data’ mentions in #deal-review.”

✨ Pro Tips

  • Double-check your Slack App’s permissions to read channel messages.
  • Use the Insert Input button to map @Keyword or channel names into downstream steps.
  • Limit channels to those used by GTM teams to reduce irrelevant triggers.

⚠️ Important Considerations

  • High-volume channels can generate many events—use specific keywords to avoid noise.
  • Bot messages may still slip through if bots aren’t properly tagged—enable “Ignore Bots” where possible.
  • Updates to app permissions require re-authorization to continue listening.

🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
No events firingWebhook not connected or authorizedReconnect Slack App and grant message scopes.
Too many false triggersKeyword too genericRefine phrase or add unique delimiters.
Missing channel mentionsChannel not selectedAdd the channel under “Channels” and save.

📝 FAQ

You can—just invite the app into those channels and re-authorize if needed.
The node does an exact text match, so include emojis or punctuation exactly as used.
This is a trigger node, since it kicks off your workflow when the keyword appears.

💰 Pricing

ActionCredit Cost
Trigger Run (per event)1 credit
Trigger nodes that start workflows—like this keyword monitor—cost 1 credit per event. All other data enrichment or formatting nodes are free.

Drop this Slack node into your flow to catch key mentions and automate your GTM alerts — automatically. 🚀