ActionSlackUpdated September 2026

How do I fetch recent messages from a Slack channel?

Short answer: You can get channel history in Slack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Slack Get Channel History action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Channel History in Slack — start free All 45 Slack actions

Get Channel History in Slack — start free

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 ID channel	string	Required	Channel ID. e.g. "C1234567890"
Limit limit	string	Optional	Number of messages (max 1000)
Oldest oldest	string	Optional	Only messages after this Unix timestamp
Latest latest	string	Optional	Only messages before this Unix timestamp

Sample request

{
  "channel": "C1234567890",
  "limit": "100",
  "oldest": "e.g. 1700000000.000000",
  "latest": "e.g. 1700100000.000000"
}

Returns

{
  "ok": true,
  "has_more": false,
  "messages": [
    {
      "ts": "1700000000.000100",
      "text": "Hello team!",
      "type": "message",
      "user": "U123"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for Get Channel History.

Any of these apps can fire this action as part of a workflow.

Gmail → Slack

1 Gmail triggers

Google Sheets → Slack

2 Google Sheets triggers

FAQ

Questions about Get Channel History.

What does the Get Channel History action do in Slack?

Retrieves recent messages from a Slack channel with pagination. Used for AI summarization, audit, or daily-digest generation.

What inputs does Get Channel History require?

Required: Channel ID. 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 run history shows the failed step with its input and the error message Slack returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Channel History support batch operations?

Run Get Channel History inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Slack's rate limits.

More actions