Get Thread Replies: Slack action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Channel channel	string	Required	Slack channel ID (starts with C for public, G for private group, D for DM). Find via List Channels. Not the channel name with #.
Thread Timestamp thread_ts	string	Required	Timestamp (`ts`) of the parent message that started the thread.
Max replies limit	number	Optional	Max number of replies to return (1–1000).

Sample request

{
  "channel": "e.g. C0123456789",
  "thread_ts": "e.g. 1709827200.123456",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "ok": true,
  "raw": {},
  "count": 3,
  "messages": []
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Thread Replies.

What does the Get Thread Replies action do in Slack?

Fetches all replies in a Slack thread. Pass the parent message's timestamp. Used to feed AI thread-summarization or for support-conversation exports.

What inputs does Get Thread Replies require?

Required: Channel, Thread Timestamp. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Slack returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Thread Replies support batch operations?

Yes. Run Get Thread Replies inside a Loop node to process arrays. Tiny Command handles Slack's rate limits automatically so you don't have to throttle manually.

More actions