Start free
ActionSlackUpdated June 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.

FieldTypeRequiredDescription
Channel ID
channel
stringRequiredChannel ID. e.g. "C1234567890"
Limit
limit
stringOptionalNumber of messages (max 1000)
Oldest
oldest
stringOptionalOnly messages after this Unix timestamp
Latest
latest
stringOptionalOnly 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
HubSpot → Slack
18 HubSpot triggers
Stripe → Slack
10 Stripe 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 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 Channel History support batch operations?
Yes. Run Get Channel History inside a Loop node to process arrays. TinyCommand handles Slack's rate limits automatically so you don't have to throttle manually.
More actions

Other Slack actions.

Action
Add Reaction
Adds an emoji reaction to a Slack message. Lightweight ack mechanism for bots, or used to seed a reaction-voting message.
Action
Raw API Request
Makes a raw authenticated call to any Slack Web API method. The escape hatch for endpoints not yet covered by a dedicated action.
Action
Archive Channel
Archives a Slack channel. Members are removed and the channel becomes read-only but recoverable; the soft alternative to deleting.
Action
Cancel Scheduled Message
Cancels a previously-scheduled Slack message before it's sent. Use it when conditions change after a Schedule Message action ran.
Action
Create Canvas
Creates a new Slack Canvas, a rich-text doc that can be shared in channels. Useful for templated onboarding docs or recurring meeting agendas.
Action
Create Channel
Creates a new Slack channel with a name and is_private flag. Used for templated channel provisioning (per-customer support channel, per-incident war room).
Get Channel History in Slack — start free