Values and tokens
Put a token in braces to insert live information into any text field.
A token is a name in braces, such as {user.name}. When a flow runs, Buildcord replaces each token with its current value. You can use tokens in almost any text field of a step.
{user.mention} just joined {server.name}, which now has {server.memberCount} members.Where tokens come from
Which tokens are available depends on the flow and on the steps before the one you're editing. The builder lists them for you when you type {.
| Group | Examples | Available |
|---|---|---|
| Command options | {option.amount} | In command flows, one for each option. |
| The event | {message.content} | In event flows. See Events. |
| The schedule | {run.time}, {run.count} | In schedule flows. |
| The button | {component.data}, {component.message} | In button action flows. |
| Earlier steps | {sent.id}, {rows.count}, {temp.total} | After the step that produces them. |
| Who and where | {user.name}, {server.name} | Everywhere. Schedules get only the server and bot values. |
| Variables | {var.score} | Everywhere, for each variable you declare. |
The full list is in the token reference.
Reaching into a value
Some values hold more than one piece. Use a dot to reach into them: {http.body.name} reads the name field of an API response, and {row.balance} reads a column of a row you found.
Secrets
Write {secret.NAME} to use a secret. Only the Send an API request step and Run code fill it in. Anywhere else the token is left empty, so a key can't end up in a message by mistake.
Time
{now} is the current time in seconds. To show it as a date in Discord, write <t:{now}:R>.
Reserved names
The names user, server, channel, member, target, option, modal, component, interaction, message, reaction, voice, thread, var, temp, loop, rows, run, now, error, http, item, sent, inserted, updated, invite, created and log belong to Buildcord. Don't use them when you name the row of a query with Read the row as.