Duaer

Integrations

Set up AgileCRM credentials in Duaer

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

Get an Agile CRM API key

The Duaer AgileCRM API credential:

  1. In Agile CRM, open Admin Settings > Developers & API, copy the REST API Key, and put it in API Key.
  2. Email is the account’s sign-in email. Subdomain is the subdomain only: for https://example.agilecrm.com, use example.

AgileCRM API fields in Duaer

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

  • Email
  • API Key (secret)
  • Subdomain: If the domain is https://example.agilecrm.com "example" would have to be entered.

Duaer nodes that use it: Agile CRM.

Save the connection in Duaer

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

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

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

In this section