Skip to main content

​
What It Does

  • Retrieves an entire conversation thread so you see context at a glance.
  • Automates follow-up tracking by pulling all replies in one go.
  • Improves visibility into deal discussions, campaign feedback, or support threads.
  • Feeds thread data into dashboards or CRM for reporting and action.

​
🏁 Getting Started

Slack Action Node config screenshot
1

Select Account

Choose your connected Slack workspace where the conversation lives.
2

Configure Inputs

Pick the channel, enter the original message timestamp, and set any paging preferences.

​
Inputs

​
🛠️ Required Fields

  • Slack (✅)
    Select your Slack app connection.
    Why it matters: Ensures the node can access the right workspace and conversation.
  • Channel (✅)
    Use the dropdown to pick a public/private channel, DM, or group.
    Why it matters: Defines where to look for the original message and thread.
  • Message Timestamp (✅)
    Enter the timestamp of the parent message (e.g., 1403051575.000407).
    Why it matters: Identifies the exact thread so you pull the right set of replies.

​
🎯 Optional Fields

  • Page Size (⚪️)
    Number of replies per page (default: 250).
    Why it matters: Control payload size if your threads are massive.
  • Number of Pages (⚪️)
    How many pages to retrieve (default: 1).
    Why it matters: Fetch more replies beyond the first batch when you need full context.

​
Output

This action returns an array of message objects from the thread, including user IDs, timestamps, and text blocks. You can feed these into downstream nodes for analysis, enrichment, or record updates.
Slack Action Node output screenshot
If multiple replies share the same field names, the node appends suffixes (e.g., text_1) to avoid collisions.

​
How It Works

  1. Uses your Slack app connection to authenticate.
  2. Calls the selected channel with the parent message timestamp.
  3. Pages through replies based on your pageSize and numPages settings.
  4. Emits a structured array of messages for downstream workflows.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Thread Review Dashboard”Pull all replies to the latest deal convo into our Salesforce op sheet.”
Campaign Feedback Sync”Fetch thread feedback in #marketing to analyze sentiment.”
Support Ticket Compilation”Aggregate user questions in a thread and post to our ticketing system.”

​
✨ Pro Tips

  • Use the Insert Input button to map @Channel or @Timestamp from upstream nodes.
  • For very long threads, bump up Number of Pages to capture older replies.
  • Combine with a filter node to only process messages from key users or containing keywords.

​
⚠️ Important Considerations

  • Very large threads may exceed rate limits—use conservative pageSize where possible.
  • Ensure your Slack app has conversations.replies scope before running.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Empty message arrayWrong channel or timestampDouble-check inputs and re-select channel
Partial thread returnedPageSize too low or numPages=1 by defaultIncrease Page Size or Number of Pages
Permission errorMissing Slack scopesGrant conversations.replies in your app settings

​
📝 FAQ

✅ Yes — as long as your Slack app and token have access to that channel.
The node only retrieves replies up to the point it runs. Re-run to get new ones.
This is an action node and runs at no credit cost. Use it as much as you like!

Ready to capture every thread reply and never miss a beat in your deal reviews? Drop this Slack node into your flow today! 🚀