Duaer

Integrations

Set up Pipedrive credentials in Duaer

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

The Duaer Pipedrive node supports two credentials:

  • Pipedrive API: in Pipedrive, click your avatar, open Personal preferences > API, copy your personal API token, and put it in API Token.
  • Pipedrive OAuth2 API: create an app in the Pipedrive Developer Hub, set Callback URL to the Duaer OAuth Redirect URL, tick the scopes for the objects the node uses, put Client ID and Client Secret in the credential, then click Connect my account.

Incoming Authentication in Pipedrive Trigger defaults to None. With Basic Auth, pick a Basic Auth credential as well: Duaer registers that user name and password on the Pipedrive webhook and rejects deliveries without them.

Pipedrive API

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

  • API Token (secret)

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

Duaer nodes that use it: Pipedrive, Pipedrive Trigger.

Pipedrive OAuth2 API

In Duaer, choose Pipedrive 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: Pipedrive, Pipedrive Trigger.

Save the connection in Duaer

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

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

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

In this section