Short answer: Drop the "Discord → Edit Message" 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 ID channel_id | string | Required | Channel ID. Example: 123456789012345678 |
Message ID message_id | string | Required | Message ID. Example: 987654321098765432 |
New Content content | string | Required | New Content |
{"channel_id": "e.g. 123456789012345678","message_id": "e.g. 987654321098765432","content": "{{trigger.content}}"}
{"id": "987654321098765432","content": "Updated message","edited_timestamp": "2025-01-15T12:00:00Z"}
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.