Integrations
Set up Salesforce credentials in Duaer
Store Salesforce 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.
Create a Salesforce connected app
Both Duaer Salesforce credentials start with a Connected App (or External Client App) in Salesforce Setup, with OAuth enabled:
- Salesforce OAuth2 API: set Callback URL to the Duaer OAuth Redirect URL and add at least the full and refresh_token OAuth scopes. Put Consumer Key and Consumer Secret in Client ID and Client Secret, then click Connect my account.
- Salesforce JWT API: suited to unattended runs. Generate a private key and certificate with openssl, turn on Use digital signatures in the app and upload the certificate, set permitted users to admin-approved, and grant the running user access to the app through a profile or permission set. In the credential, put Consumer Key in Client ID, that user name in Username, and the whole PEM private key in Private Key.
For a sandbox, set Environment Type to Sandbox.
In the JWT credential, put your My Domain address, such as https://mycompany.my.salesforce.com, in My Domain URL. The credential dialog says orgs on Spring ’26 or later need it; earlier orgs can leave it empty.
Salesforce JWT API
In Duaer, choose Salesforce JWT API when you create a credential, then fill in these fields:
- Environment Type: Default: Production. Options: Production, Sandbox.
- Client ID (required): Consumer Key from Salesforce Connected App.
- Username (required)
- Private Key (required, secret): Use the multiline editor. Make sure it is in standard PEM key format: -----BEGIN PRIVATE KEY----- KEY DATA GOES HERE -----END PRIVATE KEY-----.
- My Domain URL: Your org's My Domain URL (e.g. https://mycompany.my.salesforce.com). Required for Spring '26 and later orgs; leave blank to keep the default audience used by earlier orgs.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Salesforce, Salesforce Trigger.
Salesforce OAuth2 API
In Duaer, choose Salesforce OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
- Environment Type: Default: Production. Options: Production, Sandbox.
Duaer uses the OAuth2 PKCE 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: full refresh_token.
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.
Duaer nodes that use it: Salesforce, Salesforce Trigger.
Save the connection in Duaer
Open Credentials and create Salesforce. 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 Salesforce secret values appear in Duaer node parameters?
No. In Duaer, Salesforce secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Salesforce 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 Salesforce 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.