Short answer: Drop the "Slack → Add Reaction" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Channel channel | string | Required | Slack channel ID (starts with C for public, G for private group, D for DM). Find via List Channels. Not the channel name with #. |
Message Timestamp timestamp | string | Required | The 'ts' value of the message to react to |
Emoji Name name | string | Required | Emoji name without colons (e.g. thumbsup, not :thumbsup:) |
{"channel": "C1234567890","timestamp": "1234567890.123456","name": "e.g. thumbsup"}
{"ok": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.