Duaer

Integrations

Set up Mailchimp credentials in Duaer

Store Mailchimp 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 Mailchimp credential type

The Duaer Mailchimp node supports two credentials:

  • Mailchimp API: in Mailchimp, click your avatar, open Profile > Extras > API keys, click Create A Key, and put it in API Key. The suffix such as -us6 is the data center, and Duaer builds the API address from it, so copy the whole key.
  • Mailchimp OAuth2 API: register an app under Profile > Extras > Registered apps in Mailchimp, set Redirect URI to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, then click Connect my account.

Mailchimp API

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

  • API Key (secret)

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

Duaer nodes that use it: Mailchimp, Mailchimp Trigger.

Mailchimp OAuth2 API

In Duaer, choose Mailchimp 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.

Duaer nodes that use it: Mailchimp, Mailchimp Trigger.

Save the connection in Duaer

Open Credentials and create Mailchimp. 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 Mailchimp secret values appear in Duaer node parameters?

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

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

In this section