Duaer

Integrations

Set up Typeform credentials in Duaer

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

The Duaer Typeform node supports two credentials:

  • Typeform API: in Typeform account settings, open Personal tokens and generate a token with at least forms:read, webhooks:read, and webhooks:write, then put it in Access Token.
  • Typeform OAuth2 API: register an app under Developer apps in Typeform, set Redirect URI to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, then click Connect my account. The default scopes cover Typeform Trigger, so you rarely need Custom Scopes.

Typeform Trigger registers a webhook on the form, so Duaer must be reachable from the internet.

Typeform API

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

Typeform OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Custom Scopes: Define custom scopes. Default: off.
  • Enabled Scopes: Scopes that should be enabled. Default: webhooks:write webhooks:read forms:read. Shown when Custom Scopes is 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: webhooks:write webhooks:read forms:read.

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

Save the connection in Duaer

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

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

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

In this section