Integrations
Set up Discord credentials in Duaer
Store Discord connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
Choose a Discord connection type
The Duaer Discord node supports three credentials. Pick by what you need:
- Discord Webhook: post to one channel only. In Server Settings > Integrations > Webhooks, create a webhook and copy its Webhook URL into the credential.
- Discord Bot API: read and write channels or manage members and roles. In the Discord Developer Portal, create an application, open Bot, click Reset Token, and copy it into Bot Token. Then use OAuth2 > URL Generator with the bot scope and the permissions you need, and open the link to add the bot to your server.
- Discord OAuth2 API: authorize with OAuth and add the bot to a server. Fill in the application Client ID and Client Secret, and register the Duaer OAuth Redirect URL under the application’s OAuth2 Redirects.
Application ID and Public Key are needed only when Discord is an agent channel. Both are on the application General Information page.
Discord Bot API
In Duaer, choose Discord Bot API when you create a credential, then fill in these fields:
- Bot Token (required, secret)
- Application ID: Only needed when using Discord as an agent channel. Found on the application General Information page.
- Public Key (secret): Only needed when using Discord as an agent channel. Used to verify Discord interaction signatures.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Discord.
Discord OAuth2 API
In Duaer, choose Discord OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
- Bot Token (secret)
- Custom Scopes: Define custom scopes. Default: off.
- Enabled Scopes: Scopes that should be enabled. Default: identify guilds guilds.join bot. Shown when Custom Scopes is on.
Duaer uses the OAuth2 Authorization Code grant for this type.
In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.
By default, Duaer requests these scopes: identify guilds guilds.join bot.
Optional settings shared by every Duaer OAuth2 credential: Authentication, Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.
Duaer nodes that use it: Discord.
Discord Webhook
In Duaer, choose Discord Webhook when you create a credential, then fill in these fields:
- Webhook URL (required, secret)
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Discord.
Save the connection in Duaer
Open Credentials and create Discord. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.
Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.
Who can use this credential
Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
Questions
Do Discord secret values appear in Duaer node parameters?
No. In Duaer, Discord secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Discord credential from saving in Duaer?
Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Discord expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.