Duaer

Integrations

Set up SurveyMonkey credentials in Duaer

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

The Duaer SurveyMonkey Trigger supports two credentials. Both start with an app in the SurveyMonkey developer console:

  • SurveyMonkey API: copy Access Token, Client ID, and Client Secret from the app Settings. The token needs these scopes: Create/modify webhooks, View webhooks, View surveys, View collectors, View responses, View response details. Client ID and Client Secret verify the webhook signature.
  • SurveyMonkey OAuth2 API: in the app Settings, set OAuth Redirect URL to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, then click Connect my account.

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

SurveyMonkey API

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

  • Access Token (secret): The access token must have the following scopes: Create/modify webhooks View webhooks View surveys View collectors View responses View response details.
  • Client ID
  • Client Secret (secret)

Duaer nodes that use it: SurveyMonkey Trigger.

SurveyMonkey OAuth2 API

In Duaer, choose SurveyMonkey 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: surveys_read collectors_read responses_read responses_read_detail webhooks_write webhooks_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: SurveyMonkey Trigger.

Save the connection in Duaer

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

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

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

In this section