How to use it
- Add it from Server actionsOpen the node library and choose Support ticket from Server actions.
- Connect the workflow pathConnect Flow in from the previous step and Flow to the next step.
- Choose settings and connect valuesSet Channel, Intro Message, Name, Source. 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 |
|---|---|---|
| Channel | Not set | Used when Channel ID is not connected from an earlier node. |
| Intro Message | Thanks, a helper will be with you shortly. | Used when Intro message is not connected from an earlier node. |
| Name | ticket | Used when Thread name is not connected from an earlier node. |
| Source | event_channel | Chooses where the ticket thread is created. |
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
OptionalThread nameText
RequiredIntro messageText
OptionalOutputs
Thread IDChannel
OptionalWhat 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. The resulting Thread ID can be connected to later nodes.
You can use this item in a published BotFrame workflow. You can also test it in the simulator.