SurveyMonkey

SurveyMonkey is a cloud-based survey software tool that helps users create, send and analyze surveys. Organizations can email surveys to respondents and post them on their websites and/or social media profiles to increase response rate.

In order to integrate SurveyMonkey with Relyance AI you will need a SurveyMonkey Client ID and Client Secret.

In SurveyMonkey:

1. Login to your SurveyMonkey account.
2. Scroll to the bottom of the page and click on the Developers link.

3. Click on My Apps tab at the top.
4. Click on Add a New App.
5. Give your app a nickname and an app type. It doesn’t really matter but you can select private.

This app will be active as a draft for 90 days. After that you will need to create a new one (unless you deploy it and have an actual private SurveyMonkey app). 6. Click the Create App button. 7. Once you create it you should end up on this page:

8. Copy the Client ID and Client Secret values from this page to be used in Relyance AI.
9. Click on the Settings tab on this page.
10. In the section labeled OAuth Redirect URL paste this value: https://root.relyance.ai/api/oauth2
11. Click Submit Changes to save the redirect info.
12. Scroll down to the Scopes section and update the View Surveys, View Collectors, View Users, View Contacts and View Groups scopes to Required.

13. Click Update Scopes to save your scope changes.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the SurveyMonkey integration card and click it to open its connections.
6. Under Authentication Method, choose OAuth2 / App Token.
7. Paste the Client ID and Client Secret into their respective fields.

9. Click Authenticate.
10. At this point, you should see the following result on the Vendor Integrations page:

11. Congratulations, you are now connected to SurveyMonkey.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A feature you enabled returns nothing. Some scopes belong to a feature rather than to the connection: Data subject requests needs users_read, contacts_read, contacts_write, responses_read. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
3. A credential rotated at the vendor is not picked up here. Client Secret is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example surveymonkey/<connection_id>) or reading it with the relyance_integration_connection data source.