Duaer

Integrations

Set up Webflow credentials in Duaer

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

The Duaer Webflow node supports two credentials:

  • Webflow API: in Webflow, open the site’s Site settings > Apps & integrations > API access, click Generate API token with at least CMS read and write, Sites read, and Forms read, and put it in Access Token. The token works for that one site only.
  • Webflow OAuth2 API: create an app under Workspace settings > Apps & integrations in Webflow, set Redirect URI to the Duaer OAuth Redirect URL, and put Client ID and Client Secret in the credential. For a new app, turn Legacy off so Duaer requests cms:read, cms:write, sites:read, and forms:read.

Webflow API

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

  • Access Token (secret)

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

Duaer nodes that use it: Webflow, Webflow Trigger.

Webflow OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Legacy: If the legacy API should be used. Default: on.

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: :.

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: Webflow, Webflow Trigger.

Save the connection in Duaer

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

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

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

In this section