BotFrame

Logic · Workflow node

Cooldown

The Cooldown node as it appears in the workflow editor.

What it does

Limit how often a path can run.

When the workflow reaches this node, it uses the configured and connected values, completes its action, and follows the appropriate outgoing connection.

Typical use

Stop a command from being run repeatedly by the same user.

How to use it

  1. Add it from LogicOpen the node library and choose Cooldown from Logic.
  2. Connect the workflow pathConnect Flow in from the previous step and Flow to the next step.
  3. Choose settings and connect valuesSet On Cooldown, Scope, Seconds. 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.

SettingStarting valueWhat it controls
On CooldownstopChooses what happens when the limit has not yet expired.
ScopeuserChooses whether the limit is tracked for each user, channel, server, or bot.
Seconds60Used when Seconds 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

SecondsNumber
Required

Outputs

This item has no separate value output. Its Flow connection continues the workflow.

What happens when it runs

When the workflow reaches this node, it uses the configured and connected values, completes its action, and follows the appropriate outgoing connection.

You can use this item in a published BotFrame workflow. You can also test it in the simulator.

These details match the node currently available in the BotFrame workflow editor.