> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SurveyMonkey Webhook Setup Guide

> Configure SurveyMonkey to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](https://docs.stackone.com/connectors/surveymonkey.md#getting-started) on the SurveyMonkey connector page.

## Subscribe via the StackOne dashboard

This connector uses **Programmatic Webhooks**. When you enable webhook events on a connected SurveyMonkey account, StackOne registers one SurveyMonkey webhook per enabled event for you.

**1. Check scopes**

Make sure the connected application has the `webhooks_read` and `webhooks_write` scopes enabled. Without `webhooks_write`, subscription creation fails.

**2. Choose the surveys to watch**

Put the IDs of the surveys you want events for into the **Survey IDs** config field, separated by commas. SurveyMonkey only sends response, collector, survey updated and survey deleted events for surveys a webhook names explicitly, with no account-wide or wildcard option, so this field tells StackOne which surveys to register the webhooks against.

<ul>
  <li>Find a survey ID with the connector's `list_surveys` action.</li>
  <li>With the field empty, only Survey Created is registered.</li>
  <li>To watch another survey later, add its ID to this field. StackOne re-registers the subscriptions.</li>
</ul>

**3. Select event subscriptions in the dashboard**

In the StackOne dashboard, open the SurveyMonkey connector profile and enable the webhook events you want delivered downstream. See the **Available Webhook Events** section below for the full list. Changing the selection re-registers the affected webhooks, and disconnecting the account deletes every StackOne-managed webhook.

## Available Webhook Events

The following SurveyMonkey events can be enabled.

**1. Response events**

Events fired as respondents move through a survey. Filtered to the surveys named in the config field.

<ul>
  <li>**Response Created** (`response_created`) - Fired when a respondent starts a survey response</li>
  <li>**Response Completed** (`response_completed`) - Fired when a respondent submits a finished response</li>
  <li>**Response Updated** (`response_updated`) - Fired when an existing response is changed</li>
  <li>**Response Disqualified** (`response_disqualified`) - Fired when a disqualification rule rejects a response</li>
  <li>**Response Deleted** (`response_deleted`) - Fired when a response is deleted</li>
  <li>**Response Over Quota** (`response_overquota`) - Fired when a response exceeds a survey quota</li>
</ul>

**2. Survey events**

Events on surveys themselves.

<ul>
  <li>**Survey Created** (`survey_created`) - Fired when a survey is created. Not filtered by survey, so it covers every new survey in the account</li>
  <li>**Survey Updated** (`survey_updated`) - Fired when a watched survey is changed</li>
  <li>**Survey Deleted** (`survey_deleted`) - Fired when a watched survey is deleted</li>
</ul>

**3. Collector events**

Events on the collectors that distribute a watched survey.

<ul>
  <li>**Collector Created** (`collector_created`) - Fired when a collector is added to a survey</li>
  <li>**Collector Updated** (`collector_updated`) - Fired when a collector is changed</li>
  <li>**Collector Deleted** (`collector_deleted`) - Fired when a collector is deleted</li>
</ul>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.