Flow reference: Discord Data
Get Member
Fetch a server member.
Fetch a server member.
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
User — user
Choose the target user. {user} may be a command's selected user; {author} is the caller. Use an ID or the variable picker rather than a display name.
Input: Text with variable suggestions.
Default:
{user}.Store as — storeAs
Choose a short result prefix such as result. Later blocks must use this same prefix and run after this block. It is not a Discord channel or a persistent table.
Input: Text.
Default:
member.Outputs and next steps
out: Continue to the next step.Read the result after this block, using its configured prefix and the fields supported by the selected operation. Do not assume every response has a text or id field.
Test and troubleshoot
Invoke the correct trigger with simple inputs and verify the expected effect. Confirm variables exist on this path. A preview alone does not verify Discord delivery.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).