Duaer

Integrations

Set up Acuity Scheduling credentials in Duaer

Store Acuity Scheduling 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 an Acuity Scheduling credential type

The Duaer Acuity Scheduling Trigger supports two credentials:

  • Acuity Scheduling API: in Acuity, open Integrations > API and copy User ID and API Key into the credential.
  • AcuityScheduling OAuth2 API: register an OAuth app on the Acuity developer page, set Redirect URI to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, then click Connect my account.

Acuity Scheduling Trigger registers a webhook with the service, so Duaer must be reachable from the internet.

Acuity Scheduling API

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

  • User ID
  • API Key (secret)

Duaer nodes that use it: Acuity Scheduling Trigger.

AcuityScheduling OAuth2 API

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

By default, Duaer requests these scopes: api-v1.

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: Acuity Scheduling Trigger.

Save the connection in Duaer

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

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 Acuity Scheduling secret values appear in Duaer node parameters?

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

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

In this section