Duaer

Integrations

Set up Facebook Graph credentials in Duaer

Store Facebook Graph 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.

Use a Facebook app access token

The Duaer Facebook Trigger subscribes to webhooks through your app, so it needs app-level credentials:

  • Facebook Graph API (App): put an app access token in Access Token; you can write it as app-id|app-secret, both found under Settings > Basic in the Meta app. App Secret is optional; when set, Duaer signs calls and verifies incoming webhooks.
  • Facebook Graph (App) OAuth2 API: create an app on Meta for Developers, add Facebook Login for Business, put the Duaer OAuth Redirect URL in Valid OAuth Redirect URIs in its settings, put App ID and App Secret in Client ID and Client Secret, then click Connect my account. App Secret is again optional and verifies webhooks.

APP ID in the Facebook Trigger node is the same app’s ID. Meta requires a public HTTPS webhook address.

Facebook Graph API (App)

In Duaer, choose Facebook Graph API (App) when you create a credential, then fill in these fields:

  • Access Token (secret)
  • App Secret (secret): (Optional) When set, the node will sign API calls and verify incoming webhook payloads for added security.

Duaer nodes that use it: Facebook Trigger.

Facebook Graph (App) OAuth2 API

In Duaer, choose Facebook Graph (App) OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)
  • Custom Scopes: Whether to define custom OAuth2 scopes instead of the defaults. Default: off.
  • Enabled Scopes: Space-separated list of OAuth2 scopes to request. Default: a preset value. Shown when Custom Scopes is on.
  • App Secret (secret): (Optional) When set, the node will verify incoming webhook payloads for added security.

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.

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

Save the connection in Duaer

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

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

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

In this section