List Channels: Discord 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
Server (Guild) ID guild_id	string	Required	Server (Guild) ID. Example: 123456789012345678

Sample request

{
  "guild_id": "e.g. 123456789012345678"
}

Returns

[
  {
    "id": "chan123",
    "name": "general",
    "type": 0,
    "position": 0
  }
]

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

FAQ

Questions about List Channels.

What does the List Channels action do in Discord?

Lists all channels in a Discord server (guild) with their type, name, and parent category. Used to populate a channel picker.

What inputs does List Channels require?

Required: Server (Guild) 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 Discord 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 List Channels support batch operations?

Yes. Run List Channels inside a Loop node to process arrays. Tiny Command handles Discord's rate limits automatically so you don't have to throttle manually.

More actions