Add Member Role
discord.add_member_role
ActionChat & messagingconnection required
Calls the Discord API with the connection's credentials.
Give a server member a role.
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
4 fields, 3 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 | — | — | — |
user_id Id of the member's Discord user account. | string | Yes | — | — | — |
role_id Id of the role to grant or take away. | string | Yes | — | — | — |
reason Why the change was made; recorded in the server's audit log. | string | No | — | ≤ 512 characters | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True once Discord accepted the call. | boolean | true |
guild_id Server the role was granted in. | string | — |
user_id Member who was given the role. | string | — |
role_id Role that was granted. | string | — |
{
"guild_id": "",
"ok": true,
"role_id": "",
"user_id": ""
}Notes
- Needs a Discord connection whose secret is the bot token.
- Needs MANAGE_ROLES, and the bot's own highest role must sit above the role it is granting.
See Add Member Role 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.