How to use it
- Add it from Server actionsOpen the node library and choose Set channel permissions from Server actions.
- Connect the workflow pathConnect Flow in from the previous step and Flow to the next step.
- Choose settings and connect valuesSet Allowed permissions, Channel, Denied permissions, Role, Apply to, and the remaining options. Connections can also supply values produced by earlier nodes.
Settings
These are the options shown when you add this node. A connected value can replace a setting when the workflow runs.
| Setting | Starting value | What it controls |
|---|---|---|
| Allowed permissions | None | Selects the channel permissions to grant. |
| Channel | Not set | Used when Channel ID is not connected from an earlier node. |
| Denied permissions | None | Selects the channel permissions to remove. |
| Role | Empty | Used when Role ID is not connected from an earlier node. |
| Apply to | role | Chooses whether the permission change applies to a member or role. |
| User | Not set | Used when User ID is not connected from an earlier node. |
Value connections
Value connections pass information between nodes without changing the order of the workflow. When an input is not connected, BotFrame uses the value selected in the node or details from the starting Discord event when available.
Inputs
Channel IDChannel · Defaults to the current event channel
OptionalRole IDRole
OptionalUser IDUser · Defaults to the member who started the workflow
OptionalOutputs
This item has no separate value output. Its Flow connection continues the workflow.
What happens when it runs
When the workflow reaches this node, BotFrame uses the current server details and any connected IDs to perform the Discord action. After the action completes, the workflow continues through Flow.
You can use this item in a published BotFrame workflow. You can also test it in the simulator.