Send Message: Discord action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Channel ID channel_id	string	Required	The Discord channel snowflake ID
Message Content content	string	Required	Message text (supports Discord Markdown, max 2000 chars)
Text-to-Speech tts	options	Optional	Text-to-Speech. Options: No, Yes

Sample request

{
  "channel_id": "e.g. 123456789012345678",
  "content": "e.g. Hello from the bot! :wave:",
  "tts": "{{trigger.tts}}"
}

Returns

{
  "id": "msg123",
  "author": {
    "id": "bot123",
    "username": "MyBot"
  },
  "content": "Hello from the bot!",
  "timestamp": "2025-01-15T12:00:00.000000+00:00",
  "channel_id": "123456789012345678"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Send Message.

What does the Send Message action do in Discord?

Sends a message to a Discord channel via the bot, with optional embeds, components (buttons/select menus), and reply target. The default Discord notification action.

What inputs does Send Message require?

Required: Channel ID, Message Content. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Discord returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Send Message support batch operations?

Yes. Run Send Message inside a Loop node to process arrays. Tiny Command handles Discord's rate limits automatically so you don't have to throttle manually.

More actions