Duaer

Integrations

Set up Figma credentials in Duaer

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

The Duaer Figma Trigger supports two credentials:

  • Figma API: in Figma, open Settings > Security > Personal access tokens, generate a token with webhook read and write scopes, and put it in Access Token.
  • Figma OAuth2 API: create an app in Figma developers, set Callback URL to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, then click Connect my account.

Figma Trigger (Beta) registers a webhook with the service, so Duaer must be reachable from the internet.

Figma API

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

  • Access Token (secret)

Duaer nodes that use it: Figma Trigger (Beta).

Figma OAuth2 API

In Duaer, choose Figma 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:read webhooks:write. 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:read webhooks:write.

Optional settings shared by every Duaer OAuth2 credential: Auth URI Query Parameters, Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Figma Trigger (Beta).

Save the connection in Duaer

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

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

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

In this section