Duaer

Integrations

Set up Slack credentials in Duaer

Store Slack 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.

Using an API token

The Duaer Slack API credential uses the token you get when you install a Slack app:

  1. In Slack API Apps, create an app and pick a workspace.
  2. Open OAuth & Permissions and add the scopes your operations need under Scopes, such as chat:write and channels:read.
  3. Click Install to Workspace and allow.
  4. Copy the Bot User OAuth Token (xoxb-) or User OAuth Token (xoxp-) into Access Token in the Duaer credential.

Before a bot token posts to a channel, invite the app to that channel. For Slack Trigger, put the Signing Secret from Basic Information into Signature Secret.

Slack API

In Duaer, choose Slack API when you create a credential, then fill in these fields:

  • Access Token (required, secret): In your Slack app, open OAuth & Permissions. Copy the Bot User OAuth Token (xoxb-) or User OAuth Token (xoxp-), depending on the operations you need.
  • Signature Secret (secret): The signature secret is used to verify the authenticity of requests sent by Slack.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Slack, Slack Trigger.

Slack Manager OAuth2 API

In Duaer, choose Slack Manager OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)

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.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Slack OAuth2 API

In Duaer, choose Slack OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)
  • Signature Secret (secret): The signing secret is used to verify the authenticity of requests sent by Slack.
  • Custom Scopes: Define custom scopes. Default: off.
  • User Scope: Space-separated user-level scopes for your Slack app. Default: a preset value. 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.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Note from the dialog: If you get an Invalid Scopes error, make sure you add the correct one here (https://doc.duaer.com/integrations/builtin/credentials/slack/#using-oauth2) to your Slack integration.

Duaer nodes that use it: Slack.

Save the connection in Duaer

Open Credentials and create Slack. 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.

Using OAuth2

The Duaer Slack OAuth2 API credential needs a Slack app Client ID and Client Secret:

  1. In Slack API Apps, choose Create New App > From scratch and pick a workspace.
  2. Open OAuth & Permissions, add the OAuth Redirect URL shown in the Duaer credential dialog under Redirect URLs, and save.
  3. Add the scopes Duaer requests (below) under User Token Scopes.
  4. Copy Client ID and Client Secret from Basic Information > App Credentials into the Duaer credential, then click Connect my account and allow.

Duaer requests these user scopes by default: channels:read, channels:write, channels:history, chat:write, files:read, files:write, groups:read, groups:write, groups:history, im:read, im:history, mpim:read, mpim:history, reactions:read, reactions:write, stars:read, stars:write, usergroups:read, usergroups:write, users.profile:read, users.profile:write, users:read, users:read.email, search:read.public, search:read.private, search:read.im, search:read.mpim, search:read.

Invalid Scopes means the Slack app is missing one of them; add it. To request fewer, turn on Custom Scopes in the credential and edit User Scope (space-separated).

For Slack Trigger or approvals inside Slack, also put the app Signing Secret (Basic Information > App Credentials) in Signature Secret.

Questions

Do Slack secret values appear in Duaer node parameters?

No. In Duaer, Slack secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Slack 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 Slack expects, then confirm you can create credentials in that project.

In this section