Skip to main content

​
What It Does

  • Automatically kicks off workflows whenever a message is starred or saved in Slack
  • Ensures your team captures critical context for deals, campaigns, or support cases
  • Eliminates manual checks—stay up-to-date on important notes and references
  • Feeds saved-message details into CRM, ticketing, or reporting pipelines

​
🏁 Getting Started

Slack Node config screenshot
1

Select Account

Choose your connected Slack workspace where saved messages should be monitored.
2

Configure Inputs

No additional fields needed—this trigger fires on every saved message.

​
Inputs

​
🛠️ Required Fields

  • Select Account (✅)
    Pick the Slack workspace you want to watch for saved messages.
    Why it matters: Ensures the right channel of communication is monitored—so you never miss a saved note that impacts your pipeline or support cases.

​
🎯 Optional Fields

None

​
Output

This node emits a structured event each time someone saves (stars) a message in Slack. You’ll receive:
  • Message text
  • User who saved it
  • Channel and timestamp
Use these fields downstream to automate tasks like updating deal records, alerting stakeholders, or logging feedback.
Slack Node output screenshot
If the same message is saved multiple times, each event is emitted separately.

​
How It Works

  1. Connects to your selected Slack workspace.
  2. Listens for “save” (star) actions on messages.
  3. Captures message details and user metadata.
  4. Emits a clean payload for downstream automation (CRM updates, alerts, dashboards).

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Sales Context Capture“Log saved messages to CRM as call notes.”
Post-mortem Reporting“Trigger a report when support saves feedback in #support.”
Deal Handoff Alerts“Notify ops channel when an AE saves a negotiation update.”

​
✨ Pro Tips

  • Pinpoint team knowledge by saving messages in relevant channels and routing them automatically.
  • Use @ColumnName inputs to map message fields into your CRM or databases.
  • Filter downstream logic by user role or channel to reduce noise.

​
⚠️ Important Considerations

  • Workspaces with very high message volume may see increased credit usage.
  • Ensure your Slack app has the “channels:read” and “stars:read” scopes.
  • Deprecated endpoints may change—reconnect the Slack app periodically.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
No events showing upApp scopes missing or expiredReinstall or refresh Slack app authorization
Wrong workspace monitoredSelected account mismatchUpdate the “Select Account” field
Duplicate eventsMessage re-saved by same user/actionDeduplicate downstream or add a filter step

​
📝 FAQ

Not directly here—use a downstream filter node to screen by @channel or @user attributes.
Slack’s native star/save action triggers this node—reactions and pins are not included.
This is a trigger node, as it emits events when messages are saved in Slack.

​
💰 Pricing

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

Drop this Slack node into your flow to capture saved messages and supercharge your sales and ops workflows—automatically. 🚀