How to use it
- Add it as the workflow startChoose Button or select used when creating the workflow’s Discord event.
- Connect the workflow pathConnect its Flow output to the first node that should run.
- Choose settings and connect valuesSet Component type, Custom ID, Event value. Connections can also supply values produced by earlier nodes.
Settings
These are the options shown when you add this trigger. A connected value can replace a setting when the workflow runs.
| Setting | Starting value | What it controls |
|---|---|---|
| Component type | button | Chooses the Discord interaction that starts the workflow. |
| Custom ID | open_ticket | Matches this workflow with the corresponding Discord button, menu, or form. |
| Event value | custom_id | Chooses which detail from the Discord event is provided to the workflow. |
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
This trigger gets its information from the Discord event that starts the workflow.
Outputs
User IDUser
OptionalUser mentionUser
OptionalChannel IDChannel
OptionalGuild IDServer
OptionalComponent valueText
OptionalWhat happens when it runs
When the selected Discord event happens, this trigger starts the workflow and makes User ID, User mention, Channel ID, Guild ID, Component value available to connected nodes.
You can use this item in a published BotFrame workflow. You can also test it in the simulator.