Get Channel: 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 ID 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 #.
Include Member Count include_num_members	options	Optional	Include Member Count. Options: Yes, No

Sample request

{
  "channel": "C1234567890",
  "include_num_members": "{{trigger.include_num_members}}"
}

Returns

{
  "ok": true,
  "channel": {
    "id": "C1234567890",
    "name": "general",
    "topic": {
      "value": "Company-wide announcements"
    },
    "purpose": {
      "value": "General discussion"
    },
    "is_channel": true,
    "is_private": false,
    "num_members": 42
  }
}

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

FAQ

Questions about Get Channel.

What does the Get Channel action do in Slack?

Retrieves detailed information about a Slack channel (name, topic, purpose, members, is_archived). Used to enrich a trigger or render a channel-detail view.

What inputs does Get Channel 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 support batch operations?

Yes. Run Get Channel 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