List Members
discord.list_members
ActionChat & messagingconnection required
Calls the Discord API with the connection's credentials.
List the members of a server, in ascending user-id order.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Discord
- Secret shape
- the bot token (sent as "Authorization: Bot <token>") for every op except discord.execute_webhook, whose secret is the webhook URL
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
guild_id Id of the Discord server (right-click the server → Copy Server ID). | string | Yes | — | — | — |
limit How many members to return, 1-1000. | number | No | 100 | 1–1000 | — |
after Return members whose user id is above this one, to page. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"limit": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The objects Discord returned, in its own order. | array | — |
count How many objects came back in this page. | number | — |
{
"count": 0,
"items": []
}Notes
- Needs a Discord connection whose secret is the bot token.
- Needs the privileged SERVER MEMBERS intent, switched on for the application in the Discord Developer Portal.
- Discord caps a page at 1000: to read the rest, feed the user.id of the last member you got back into 'after'.
- Discord rate limits per route: a 429 is reported with the retry_after it asked for, so pace a loop over this node with control.delay.
See List Members run in a workflow.
In a technical demo we add the Discord connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.