Every flow has exactly one trigger, the first box on its canvas. Click it to choose what starts the flow and its settings, like which button or the command's name.

What it gives you

A trigger gives the steps after it values about what happened: who clicked, which channel, the message they sent. They show as coloured pins on its right side. Wire one into a step's setting to use it.

Event triggers

Server events (a ban, a channel created, a boost) start flows too. They need the Basic plan, and a few need the bot to have Discord's member or message content access turned on.

Command options

A command's options can be text, a member, a user (anyone, even someone who isn't in the server, like for /unban), a channel, a role, a file, a number or yes/no. A file option gives its link, file name, size in bytes and file type as pins. An optional option left blank is empty: check it with Is empty.

Names the bot already uses

A few command names, like /warn, /ban or /rank, belong to the bot's own features, and a server only sees them while that feature is on. Your own command can use one of those names: it replaces the built-in in your server while your flow is on, and the trigger says so.

What the posting run knew

A click on a button or menu can read the values of the run that posted its message: {origin.trigger.prize}, {origin.user.name}, {origin.var.note} or {origin.node.<id>.<value>}. No table keyed by message id needed. Messages posted before this (or too long ago) leave {origin...} as typed.