Discord

Send messages, manage guilds, and interact with Discord via the Bot API.

Detail	Value
Category	Communication
Base URL	`https://discord.com/api/v10`
Authentication	Bearer Token
Endpoints	6
Connector key	`discord`

Using Discord in a workflow

Go to Connections and click New Connection.
Pick Discord from the marketplace.
Enter your credentials (see Authentication above for what's expected).
In a workflow, drop an API Call node and select this connection.
Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
`POST /channels/{channel_id}/messages`	Send a message to a channel
`GET /channels/{channel_id}/messages`	Get channel messages
`GET /guilds/{guild_id}`	Get guild information
`GET /guilds/{guild_id}/channels`	List guild channels
`GET /guilds/{guild_id}/members`	List guild members
`PUT /channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@me`	Add a reaction to a message

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /channels/{channel_id}/messages

Send a message to a channel

Detail	Value
Operation ID	`messaging.sendMessage`
Method	`POST`
Path	`/channels/{channel_id}/messages`

Parameters

Name	Location	Type	Required
`channel_id`	path	string	Yes

Request Body

Field	Type
`content`	string
`embeds`	array

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your Discord connection from the Connection dropdown.
In the Operation dropdown, select messaging.sendMessage.
Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Discord API reference.

GET /channels/{channel_id}/messages

Get channel messages

Detail	Value
Operation ID	`messaging.getMessages`
Method	`GET`
Path	`/channels/{channel_id}/messages`

Parameters

Name	Location	Type	Required
`channel_id`	path	string	Yes
`limit`	query	integer	No

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your Discord connection from the Connection dropdown.
In the Operation dropdown, select messaging.getMessages.
Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Discord API reference.

GET /guilds/{guild_id}

Get guild information

Detail	Value
Operation ID	`messaging.getGuild`
Method	`GET`
Path	`/guilds/{guild_id}`

Parameters

Name	Location	Type	Required
`guild_id`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your Discord connection from the Connection dropdown.
In the Operation dropdown, select messaging.getGuild.
Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Discord API reference.

GET /guilds/{guild_id}/channels

List guild channels

Detail	Value
Operation ID	`messaging.getGuildChannels`
Method	`GET`
Path	`/guilds/{guild_id}/channels`

Parameters

Name	Location	Type	Required
`guild_id`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your Discord connection from the Connection dropdown.
In the Operation dropdown, select messaging.getGuildChannels.
Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Discord API reference.

GET /guilds/{guild_id}/members

List guild members

Detail	Value
Operation ID	`messaging.listMembers`
Method	`GET`
Path	`/guilds/{guild_id}/members`

Parameters

Name	Location	Type	Required
`guild_id`	path	string	Yes
`limit`	query	integer	No

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your Discord connection from the Connection dropdown.
In the Operation dropdown, select messaging.listMembers.
Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Discord API reference.

PUT /channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@me

Add a reaction to a message

Detail	Value
Operation ID	`messaging.addReaction`
Method	`PUT`
Path	`/channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@me`

Parameters

Name	Location	Type	Required
`channel_id`	path	string	Yes
`message_id`	path	string	Yes
`emoji`	path	string	Yes

Using this endpoint in a workflow

Add an API Call node to your workflow.
Pick your Discord connection from the Connection dropdown.
In the Operation dropdown, select messaging.addReaction.
Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Discord API reference.

Discord ​

Using Discord in a workflow ​

Available endpoints ​

POST /channels/{channel_id}/messages ​

Parameters ​

Request Body ​

Using this endpoint in a workflow ​

What it returns ​

GET /channels/{channel_id}/messages ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /guilds/{guild_id} ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /guilds/{guild_id}/channels ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

GET /guilds/{guild_id}/members ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

PUT /channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@me ​

Parameters ​

Using this endpoint in a workflow ​

What it returns ​

Discord

Using Discord in a workflow

Available endpoints

POST /channels/{channel_id}/messages

Parameters

Request Body

Using this endpoint in a workflow

What it returns

GET /channels/{channel_id}/messages

Parameters

Using this endpoint in a workflow

What it returns

GET /guilds/{guild_id}

Parameters

Using this endpoint in a workflow

What it returns

GET /guilds/{guild_id}/channels

Parameters

Using this endpoint in a workflow

What it returns

GET /guilds/{guild_id}/members

Parameters

Using this endpoint in a workflow

What it returns

PUT /channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@me

Parameters

Using this endpoint in a workflow

What it returns