Slack ACTION
Get Thread Replies
Retrieve all replies in a message thread. Accepts a channel ID (preferred — resolves instantly) or channel name (resolved by scanning up to 5 conversations.list pages, ~5,000 active public/private channels — a name beyond that limit returns a configuration error). To read a thread in a DM, pass the other person's user ID (e.g.
U1234567890) as the channel — pass your OWN user ID to read your conversation with yourself. Use Get Channel History or Search to find the parent message's timestamp (thread_ts). Returns the parent message followed by all replies in chronological order. Pass fields (e.g. text,ts,user) unless you need full message objects — raw Slack messages carry blocks, attachments and edit metadata, so a long thread can run to tens of thousands of characters and be truncated before you see any of it. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Slack account once, then configure and run Get Thread Replies from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "slack_v2-get-thread-replies",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
slack_v2: { authProvisionId: "apn_xxxxxxx" },
channel: "Channel",
threadTs: "Thread Timestamp",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "slack_v2-get-thread-replies",
"configured_props": {
"slack_v2": { "authProvisionId": "apn_xxxxxxx" },
"channel": "Channel",
"threadTs": "Thread Timestamp"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "slack_v2",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "slack_v2-get-thread-replies",
arguments: {
channel: "Channel",
threadTs: "Thread Timestamp",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
channel Channel | string | Prefer a channel ID (e.g. C1234567890) — use List Channels to look it up; it resolves instantly. A channel name (e.g. general or #general) is also accepted, but resolving it scans up to 5 pages (~5,000 channels) of the workspace's channel list, which can be slow — and a valid channel beyond that bound will not be found. For a DM thread, pass a user ID (e.g. U1234567890) — including your own, to read your self-DM. Required |
threadTs Thread Timestamp | string | The ts of the parent message (e.g. 1234567890.123456). Required |
limit Limit | integer | Maximum number of replies to return. Default: 50. Optional |
fields Fields | string[] | Message properties to return, e.g. text, ts, user, thread_ts, reply_count, reactions, permalink. Recommended: ["text", "ts", "user"]. Omit only when you need the full message objects. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- slack_v2-get-thread-replies
- Version
- 0.1.6
- App
- Slack
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗