Discord bot (API)

Node catalog Actions

On this page

Actions with the bot token: messages, interactions, roles, or free REST calls.

Usage and specifics

The bot token supports guided actions or a custom REST request. Interactions require identifiers and the token from the received event; bot permissions still apply.

Technical type : discord_bot. Runtime : nodulz.

Credentials and prerequisites

Create and configure the credential : discord-bot

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialSource`	`enum`	`"trigger"`	`trigger`, `explicit`
`credentialId`	`string`	-	-
`mode`	`enum`	`"operation"`	`operation`, `rest`
`operation`	`enum`	`"send_message"`	`send_message`, `reply_message`, `edit_message`, `delete_message`, `add_reaction`, `interaction_response`, `interaction_edit_original`, `interaction_followup`, `interaction_delete_original`, `member_add_role`, `member_remove_role`, `create_thread`
`channelId`	`string`	`"{{ input.channel.id }}"`	-
`messageId`	`string`	`""`	-
`guildId`	`string`	`""`	-
`userId`	`string`	`""`	-
`roleId`	`string`	`""`	-
`content`	`string`	`""`	-
`embeds`	`array`	`[]`	-
`embeds[].title`	`string`	`""`	-
`embeds[].description`	`string`	`""`	-
`embeds[].url`	`string`	`""`	-
`embeds[].color`	`string`	`""`	-
`embeds[].timestamp`	`boolean`	`false`	-
`embeds[].footer`	`string`	`""`	-
`embeds[].footerIconUrl`	`string`	`""`	-
`embeds[].imageUrl`	`string`	`""`	-
`embeds[].thumbnailUrl`	`string`	`""`	-
`embeds[].authorName`	`string`	`""`	-
`embeds[].authorUrl`	`string`	`""`	-
`embeds[].authorIconUrl`	`string`	`""`	-
`embeds[].fields`	`array`	`[]`	-
`embeds[].fields[].name`	`string`	`""`	-
`embeds[].fields[].value`	`string`	`""`	-
`embeds[].fields[].inline`	`boolean`	`false`	-
`ephemeral`	`boolean`	`false`	-
`interactionToken`	`string`	`""`	-
`interactionId`	`string`	`""`	-
`emoji`	`string`	`""`	-
`threadName`	`string`	`""`	-
`autoArchiveDuration`	`number`	-	-; ≥ 0
`interactionResponseType`	`number`	-	-
`method`	`enum`	`"GET"`	`GET`, `POST`, `PUT`, `PATCH`, `DELETE`
`path`	`string`	`""`	-
`body`	`string`	`""`	-

Examples

Example: {{ input.message.content }} or {{ input.member.username }}

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialSource": "trigger",
  "mode": "operation",
  "operation": "send_message",
  "channelId": "{{ input.channel.id }}",
  "content": "",
  "embeds": []
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.