> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/surveymonkey.md).

# SurveyMonkey

Register a SurveyMonkey app for the SurveyMonkey connector and configure its client ID and secret in the Backoffice.

The SurveyMonkey connector uses OAuth 2.0. You register an app in the SurveyMonkey Developer Portal and store its client ID and secret in the Backoffice. The triggers (**New Response**, **New Survey**) register their webhooks through the API when a flow starts; nothing has to be set up for them in the Developer Portal.

## OAuth app properties

| Property                | Value                                                                                                                                                                                                                                                                                                                     |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Conditional.** Only a **Public** app that SurveyMonkey has approved and published serves any SurveyMonkey account. A **Private** app serves only members of the SurveyMonkey team it is registered to, and every one of them needs a paid plan with API access. A draft app serves only the account that registered it. |
| **Vendor review**       | **Required** for a Public app: SurveyMonkey reviews and approves it before it is published in the App Directory. The **Create/Modify Surveys** scope (`surveys_write`), which the connector uses, needs SurveyMonkey's separate approval in a Public app. Private apps are not reviewed.                                  |
| **Review time**         | Not documented.                                                                                                                                                                                                                                                                                                           |
| **Users before review** | Only the account that registered the app (draft app). The draft is disabled after 90 days unless it is deployed as Public or Private.                                                                                                                                                                                     |
| **App owner**           | Any SurveyMonkey account can register a draft app. Deploying a Private app needs a paid plan that offers direct API access for the whole team.                                                                                                                                                                            |
| **Regions**             | Each data center (US, EU, Canada) has its own Developer Portal. The connector sends the authorization and token requests to `api.surveymonkey.com` and then calls the API host of the account's data center (`api.surveymonkey.com`, `api.eu.surveymonkey.com` or `api.surveymonkey.ca`).                                 |
| **Client secret**       | No expiry documented.                                                                                                                                                                                                                                                                                                     |
| **Rate limits**         | Draft and Private apps: 120 requests per minute and 500 per day, per app, shared by all users; the daily limit resets at 00:00 GMT. Published Public apps: no limit. Higher limits for Private apps can be bought.                                                                                                        |
| **Checked**             | 2026-11-17                                                                                                                                                                                                                                                                                                                |

**Limitations**

* The daily limit of a draft or Private app (500 requests) is shared by every connected account and every flow. The connector throttles each user to 120 requests per minute, but it cannot enforce the daily limit.
* **Get Response** and **List Responses** need the **View Response Details** scope (`responses_read_detail`), which SurveyMonkey only grants to accounts on a paid plan. On free plans **New Response** emits the response without its answers.
* **Create Collector** needs the **Create/Modify Collectors** scope (`collectors_write`); SurveyMonkey requires a paid plan for every collector type except a web link collector.
* If a scope is set to **Required** in the app settings, an account whose plan does not include it is asked to upgrade and cannot connect. Set the two scopes tied to a paid plan, **View Response Details** and **Create/Modify Collectors**, to **Optional** if free accounts should be able to connect; step 5 below lists the setting of every scope.
* SurveyMonkey's documentation does not say whether an app registered in the US Developer Portal can authorize accounts in the EU or Canada data center.
* Access tokens do not expire, and there is no refresh token. A connected account stops working when the user removes the app under **My Account** → **Linked Accounts**; the user then has to connect it again.

Sources: [SurveyMonkey API overview](https://api.surveymonkey.com/v3/docs) (Public Apps, Private Apps, Registering an App, Deploying an App, Scopes, Request and Response Limits, Authentication), [SurveyMonkey API access](https://help.surveymonkey.com/en/surveymonkey/integrations/surveymonkey-api/). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Register the app

1. Sign in to the SurveyMonkey Developer Portal of your account's data center: [developer.surveymonkey.com](https://developer.surveymonkey.com/) (US), [developer.eu.surveymonkey.com](https://developer.eu.surveymonkey.com/) (EU) or [developer.surveymonkey.ca](https://developer.surveymonkey.ca/) (Canada).
2. Open **My Apps** and click **Add a New App**.
3. Fill in **App Nickname** and **App Creator**, choose the app type (**Public App** for an app all your users can connect to, **Private App** for your own SurveyMonkey team only) and click **Create App**. SurveyMonkey creates the app as a draft.
4. Open the app's **Settings** tab. In **OAuth Redirect URL** enter

   ```
   https://<your-appmixer-api>/auth/surveymonkey/callback
   ```

   where `<your-appmixer-api>` is the host of your Appmixer API (for example `api.acme.appmixer.cloud`). Click **Submit Changes**.
5. Scroll down to **Scopes**. Every scope is **Not Required** by default; click a scope to switch it to **Required** or **Optional**. Set the scopes the connector uses as follows and leave all other scopes **Not Required**:

   | Scope                   | Label in the Developer Portal                                                          | Setting  |
   | ----------------------- | -------------------------------------------------------------------------------------- | -------- |
   | `users_read`            | View Users                                                                             | Required |
   | `surveys_read`          | View Surveys                                                                           | Required |
   | `surveys_write`         | Create/Modify Surveys                                                                  | Required |
   | `collectors_read`       | View Collectors                                                                        | Required |
   | `collectors_write`      | Create/Modify Collectors (paid SurveyMonkey plan for anything but web link collectors) | Optional |
   | `contacts_read`         | View Contacts                                                                          | Required |
   | `contacts_write`        | Create/Modify Contacts                                                                 | Required |
   | `responses_read`        | View Responses                                                                         | Required |
   | `responses_read_detail` | View Response Details (paid SurveyMonkey plans only)                                   | Optional |
   | `webhooks_read`         | View Webhooks                                                                          | Required |
   | `webhooks_write`        | Create/Modify Webhooks                                                                 | Required |

   What the settings mean:

   * **Required** — the account must have the scope, or it cannot connect: an account whose plan does not include the scope is asked to upgrade. Use it for the scopes SurveyMonkey offers on every plan, so that every connected account can run the components that need them.
   * **Optional** — the account connects with or without the scope. Use it for the two scopes tied to a paid plan, so that free accounts can still connect; the components that need the missing scope then fail with a permission error (see Limitations above). Set them to **Required** only if every user of the app is on a paid plan and you prefer the connection to be refused up front.
   * **Not Required** — the app does not ask for the scope, and no connected account gets it.

   SurveyMonkey takes the scopes from these app settings, not from the authorization request, so a scope left **Not Required** here is missing for every connected account. Click **Update Scopes**.
6. In the **Credentials** section of the **Settings** tab, copy the **Client ID** and the **Secret** (click **Show Secret**).
7. Before the 90-day draft period ends, click **Deploy** to deploy the app. A Public app is published only after SurveyMonkey has reviewed and approved it; until then only the account that registered the app can connect.

The webhook triggers need an Appmixer API reachable from the internet: SurveyMonkey checks the webhook URL with a `HEAD` request when the trigger registers it.

## Backoffice configuration

Configuration ID: `appmixer:surveymonkey` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — Client ID of the SurveyMonkey app registered above. Not needed when SurveyMonkey is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Secret of the same app. Not needed with the Auth Hub.
* `listCacheTTL` — Optional. How long, in milliseconds, the survey list of **List Surveys** is cached when it fills inspector dropdowns. The cache is kept per connected account. Default `120000` (2 minutes).
* `outputFilePrefix` — Optional. File name prefix of the CSV file that **List Surveys**, **List Responses**, **Find Contacts** and **List Contact Lists** create when their output is set to a file; the file is named `<prefix>-<component name>.csv`. Default `surveymonkey-objects-export`.

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:surveymonkey -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/surveymonkey.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
