Flow reference: Messages
Send as Webhook
Post a message with any name and avatar through a webhook the bot keeps in the channel (named Bottly). Sets {webhook.messageId}.
Post a message with any name and avatar through a webhook the bot keeps in the channel (named Bottly). Sets {webhook.messageId}.
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
Channel (blank = current) — channel
Choose the channel this block targets or filters. Use its Discord ID or a supported channel variable. Check channel overrides for the bot.
Input: Text.
Default: ``.
Shown name — username
Name shown on the webhook message instead of the bot's name. Discord refuses names containing "discord" or "clyde".
Input: Text with variable suggestions.
Default:
{server.name}.Avatar URL (https) — avatarUrl
Public https link to a picture shown as the webhook message's avatar. Blank uses the webhook's own avatar.
Input: Text.
Format example, not a ready value for your server:
https://…/avatar.png.Default: ``.
Message text — content
Enter message text and supported {variables}. Keep secrets out of visible output. Message layout is configured separately in the message editor when available.
Input: Text with variable suggestions.
Default: ``.
Allow @everyone and role pings — allowPings
Enable mass mentions only when intentional. Untrusted text should not be allowed to ping everyone or arbitrary roles.
Input: On/off switch.
Editor guidance: Off: only members can be pinged, so text from users can never mass-ping.
Message editor
Alongside ordinary fields, configure text, embeds or Components V2 in this block's message editor. Add buttons/menus in the message and match their Custom IDs to their triggers. [Message guide](/docs/design).
Outputs and next steps
out: Continue to the next step.Test and troubleshoot
Invoke the correct trigger with simple inputs and verify the expected effect. Confirm variables exist on this path. A preview alone does not verify Discord delivery.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).