Add Reaction: 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	Channel ID. Example: 123456789012345678
Message ID message_id	string	Required	Message ID. Example: 987654321098765432
Emoji emoji	string	Required	Unicode emoji (e.g. 👍) or custom emoji in name:id format

Sample request

{
  "channel_id": "e.g. 123456789012345678",
  "message_id": "e.g. 987654321098765432",
  "emoji": "e.g. 👍 or custom_emoji:123456"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Add Reaction.

What does the Add Reaction action do in Discord?

Adds an emoji reaction to a Discord message from the bot. Used as a lightweight ack or to seed a reaction-vote message.

What inputs does Add Reaction require?

Required: Channel ID, Message ID, Emoji. 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 Add Reaction support batch operations?

Yes. Run Add Reaction 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