ActionSlackUpdated May 2026

How do I rename a Slack channel?

Short answer: Drop the "Slack → Rename Channel" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 45 Slack actions

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 #.
New Name name	string	Required	Channel name (lowercase, no spaces, 1–80 chars). Slack will normalize it.

Sample request

{
  "channel": "e.g. C0123456789",
  "name": "e.g. team-updates"
}

Returns

{
  "ok": true,
  "channel": {
    "id": "C01234567",
    "name": "team-updates"
  }
}

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

Triggered by

Apps that pair well as the trigger for Rename Channel.

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 Rename Channel.

What does the Rename Channel action do in Slack?

Renames a Slack channel. Useful when channel names track sprint numbers, customers, or campaigns that change over time.

What inputs does Rename Channel require?

Required: Channel ID, New Name. 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 Rename Channel support batch operations?

Yes. Run Rename 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