Discord Bot: Send Message
Send a message to a Discord channel via an OAuth-connected bot. Supports Markdown formatting. No manual webhook setup required — just connect your Discord server and pick a channel. Ideal for: price alerts, trade notifications, portfolio updates, community announcements.
Catalog action Integrations pipedream:discord
Send a message to a Discord channel via an OAuth-connected bot. Supports Markdown formatting. No manual webhook setup required — just connect your Discord server and pick a channel. Ideal for: price alerts, trade notifications, portfolio updates, community announcements.
At a Glance
| Field | Value |
|---|---|
| Action ID | discord-bot-send-message |
| Category | Integrations |
| Connector | pipedream:discord |
| Requires gas | No |
| Funds movement | None declared |
| Tags | pipedream, integration, oauth, discord, messaging, notification, community, chat, bot, write |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
channel | string | Yes | Discord channel ID to send the message to. |
message | string | Yes | Message text to send. Supports Markdown: bold, italic, 'code', links. Max 2000 characters. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
success | boolean | Yes | Whether the message was sent successfully |
data | object | No | Discord API response data |
exports | object | No | Exported values from the action |
Examples
json{ "type": "discord-bot-send-message", "payload": { "channel": "example-channel", "message": "Workflow completed" }, "children": [], "connector": { "type": "pipedream:discord", "id": "conn_pipedream_discord" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/discord-bot-send-message/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "channel": "example-channel", "message": "Workflow completed" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.