Request Guild Members
AI-generatedSummary
Requests Discord to send guild member data through an active Discord Trigger connection. The request is sent over the Gateway; member data arrives later as a GUILD_MEMBERS_CHUNK event on the matching Trigger.
Inputs
- Connection Name — Name of the active Discord Trigger connection to use; defaults to
default. - Guild ID (required) — Guild snowflake ID to request members from.
- Query — Username prefix to match. Used when User IDs are empty; an empty query with Max Members set to 0 requests all members.
- Max Members — Maximum number of members to return; defaults to 0 (no limit). The UI describes a maximum of 100 unless User IDs are provided.
- Presences — Whether to include member presences. Requires Discord's GUILD_PRESENCES privileged intent; defaults to false.
- User IDs — Comma- or whitespace-separated user snowflake IDs to fetch. Mutually exclusive with a nonempty Query; the UI specifies a maximum of 100.
- Nonce — Optional nonce, up to 32 characters per the UI, for correlating the resulting chunk event.
Output shape
One output item per input item, confirming the request was sent.
Each successful item contains
success: true, the operation name, connection name, andsentPayload. This is not the requested member list; Discord returns that later through the matching Trigger. If Continue On Fail is enabled, failed items contain anerrorfield; otherwise execution errors. An active Trigger connection with the configured name is required.