Slack:Get Conversation History
Controlled node
Overview
Read channel messages and continue with a cursor.
Retrieve message history for a Slack conversation accessible to the selected connection.
Inputs
| Input | Type | Description |
|---|---|---|
| run | Event | Triggers this operation. |
| channelId | Text | Required conversation ID, such as C1234567890. Use the id from List Conversations. |
| limit | Number | Requested items per page. Use a positive integer up to 200. Defaults to 200; Slack may return fewer. |
| maxPages | Number | Maximum pages to fetch in this run. Use an integer from 1 to 5. Defaults to 1. |
| cursor | Text | Optional continuation cursor from the previous result’s nextCursor. Leave unset for the first request. |
Properties
| Setting | Type | Description |
|---|---|---|
| connections | Connection | Select an authenticated Slack connection from this project. Channel access depends on that connection’s permissions and membership. |
Outputs
| Output | Type | Description |
|---|---|---|
| messages | Data | Object containing a messages array and nextCursor. On failure, an object with error. This output is not itself an array. |
| done | Event | Fires when the node returns, including when it returns an error result. Check the data output before continuing. |
Pagination
The node requests up to limit × maxPages items, with a maximum of 1,000 per run. The actual count can be lower. Pass nextCursor into a later run’s cursor to continue; null means there is no further cursor.
Messages include fields such as text, user and ts where available. Keep ts as text; it can be supplied to Send Message’s threadTs. This node does not fetch every thread’s replies.
Example
Set channelId, limit: 100 and maxPages: 1, select the connection and trigger run. On done, inspect the result. Use Get Value with path messages to extract the array before passing it to For Each → object. Extract nextCursor separately if you need another page.