Reference · Credentials
Connect Discord to BusyBot
Used by 1 BusyBot node.
discordOAuth2Api 4 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Bot TokenbotToken | password | Yes | — |
Client IDclientId | string | Yes | — |
Client SecretclientSecret | password | Yes | — |
Access TokenaccessToken | password | No | — |
Setting up Discord OAuth2
- In Discord OAuth2, create the credential this connection needs — the values listed in the table above. These are issued from your own Discord OAuth2 account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Discord OAuth2.
- Paste each value into the matching field and save.
- Add the Discord node to a workflow, select this credential, and run a simple operation to confirm it authenticates.
Security
- Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
- Grant the minimum scopes or permissions the operations you actually use require.
- Rotate the credential periodically, and immediately if it may have been exposed.
- Credentials are scoped to your account — a workflow cannot use another account's.
Frequently asked questions
Which BusyBot nodes use Discord credentials?
One node: Discord. Create the credential once and select it in that node.
What does a Discord credential need?
4 fields: Bot Token, Client ID, Client Secret, Access Token. Required: Bot Token, Client ID, Client Secret. The values come from your own Discord account.
How are Discord secrets stored?
Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.
Does Discord use OAuth?
Yes. This credential connects through OAuth (fields: Bot Token, Client ID, Client Secret, Access Token): you approve access in Discord, and the resulting tokens are stored encrypted like every other credential.
Nodes that use Discord OAuth2
One credential works across every node below — create it once and reuse it.