Resources · n8n integration

SurveyMonkey n8n integrationAutomate SurveyMonkey with n8n.

Every finished response can start a workflow. The SurveyMonkey n8n integration ships as a trigger node: 12 webhook events across responses, surveys and collectors fire seconds after they happen. Built for ops and research teams done with manual CSV exports.

Try the SurveyMonkey integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the SurveyMonkey n8n integration actually do?

The SurveyMonkey n8n integration is a one-way link: SurveyMonkey pushes events to n8n, and n8n does the rest. The catalogue ships a single node, the SurveyMonkey Trigger, which listens to 12 events spread over three object types: responses, surveys and collectors. Pick the events you care about, and every workflow you draw behind the trigger runs on fresh survey data instead of an export downloaded three weeks ago.

The most common setup starts with response_completed. A respondent hits the last page, SurveyMonkey fires the event, and n8n appends a row to Google Sheets before the browser tab is even closed. Research teams use it to keep a live satisfaction tab; support teams use it to timestamp every post-ticket survey.

Panel quality is the second reason people reach for this trigger. response_disqualified tells you a response was disqualified, response_overquota tells you a response went over a survey's quota, and response_created tells you a respondent only began. Route the three into one Slack channel and the gap between started and completed stops being a monthly surprise.

The six remaining events cover objects rather than answers. survey_created, survey_updated and survey_deleted follow the life of a questionnaire; collector_created, collector_updated and collector_deleted follow the collectors, meaning the channels a survey goes out through. Writing each change to Airtable gives a team an audit trail nobody has to maintain by hand.

In n8n, SurveyMonkey comes down to this trigger. When you need a call to the SurveyMonkey API that sits outside that catalogue, the HTTP Request node takes over: it reaches any endpoint of the API and reuses the same credential through its predefined authentication. A credential, to be clear, is the access you create once in the Credentials menu of n8n and that every workflow finds again in its dropdown. Our n8n review digs into where that pattern pays off.

Two settings change what lands in your workflow. With Resolve Data off, the webhook data only contains IDs; switch it on and n8n resolves the data automatically. Only Answers returns only the answers of the form and none of the other data. The habit worth keeping: send one real test response and compare the two executions before building anything on top. The n8n training spends its first hour on exactly that.

Connect

How do you connect SurveyMonkey to n8n?

  1. 01

    Register an app in SurveyMonkey

    Start from a SurveyMonkey account, then open Developer dashboard > My apps and register an app. That app is what n8n authenticates against, whichever method you pick later. Keep the tab open: the access token, the client ID and the client secret all come from the screens of that same app once it exists.

  2. 02

    Select the six required scopes

    In the app, open Settings > Scopes and select the six scopes n8n needs: View Surveys, View Collectors, View Responses, View Response Details, Create/Modify Webhooks and View Webhooks. Save with Update Scopes. A webhook is just a URL SurveyMonkey calls when something happens, so without the two webhook scopes n8n has no right to register its own.

  3. 03

    Pick a token or OAuth2 in n8n

    Two methods work. With an API access token, copy the Access Token, Client ID and Client Secret from Settings > Credentials into the n8n credential. With OAuth2, copy the OAuth Redirect URL from n8n into Settings > Settings, select Submit Changes, paste the client ID and the secret, then select Connect my account in the n8n credential.

Triggers

What fires a SurveyMonkey workflow?

SurveyMonkey Trigger is the node that starts a workflow when something happens in SurveyMonkey. It listens to 12 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your SurveyMonkey account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

collector_created.*1
  • collector_created.
    • collector_created
collector_deleted.*1
  • collector_deleted.
    • collector_deleted
collector_updated.*1
  • collector_updated.
    • collector_updated
response_completed.*1
  • response_completed.
    • response_completed
response_created.*1
  • response_created.
    • response_created
response_deleted.*1
  • response_deleted.
    • response_deleted
response_disqualified.*1
  • response_disqualified.
    • response_disqualified
response_overquota.*1
  • response_overquota.
    • response_overquota
response_updated.*1
  • response_updated.
    • response_updated
survey_created.*1
  • survey_created.
    • survey_created
survey_deleted.*1
  • survey_deleted.
    • survey_deleted
survey_updated.*1
  • survey_updated.
    • survey_updated

Configuration notes

01Configure the SurveyMonkey TriggerOne node covers the whole integration. Drop the SurveyMonkey Trigger on the canvas, pick what it should listen to, activate the workflow, and n8n registers its webhook URL with SurveyMonkey. Events then arrive within seconds, with nothing to schedule on your side.

One node covers the whole integration. Drop the SurveyMonkey Trigger on the canvas, pick what it should listen to, activate the workflow, and n8n registers its webhook URL with SurveyMonkey. Events then arrive within seconds, with nothing to schedule on your side.

Key parameters

  • Type: the object you watch. It decides which of the 12 events the Event list offers next.
  • Event: the event that starts the workflow. There is no catch-all value, so one node listens to one event and you duplicate the node to follow a second one.
  • Survey Names or IDs and Survey Name or ID: the surveys in scope, chosen from the list or passed as an expression such as {{ $json.field }}.
  • Collector Names or IDs: the collectors in scope, same list or expression.
  • Resolve Data: off, the webhook data only contains IDs; on, n8n resolves the data automatically.
  • Only Answers: returns only the answers of the form and none of the other data.
Use cases
a first workflow that listens to one event and logs the raw item, so you see what SurveyMonkey sends before wiring anything behind it.
02Response EventsSix of the 12 events describe what a respondent does. response_created fires when a respondent begins a survey, response_completed when the response is completed, response_updated when it is updated afterwards, response_deleted when it is deleted. response_disqualified covers a response that gets disqualified, response_overquota a response that goes over a survey's quota.

Six of the 12 events describe what a respondent does. response_created fires when a respondent begins a survey, response_completed when the response is completed, response_updated when it is updated afterwards, response_deleted when it is deleted. response_disqualified covers a response that gets disqualified, response_overquota a response that goes over a survey's quota.

Key parameters

  • Survey Names or IDs: limits the trigger to the questionnaires you care about instead of every survey in the account.
  • Only Answers: keeps the item down to the answers of the form, which is what a scoring or routing branch usually needs.
When to use it
whenever a survey result has to reach a person or another tool the same day.
Use cases
a completed satisfaction survey that lands in a shared sheet, and a disqualified response that quietly feeds a screening counter.
03Survey EventsThe questionnaire itself has its own three events. survey_created fires when a survey is created, survey_updated when a survey is updated, survey_deleted when one is deleted. None of them carries an answer: they tell you the object changed, which is precisely what a governance workflow needs.

The questionnaire itself has its own three events. survey_created fires when a survey is created, survey_updated when a survey is updated, survey_deleted when one is deleted. None of them carries an answer: they tell you the object changed, which is precisely what a governance workflow needs.

Key parameters

  • Type: set to the survey object so the Event list offers these three.
  • Resolve Data: left off when an ID is enough for the log, switched on when the next node needs more than an identifier.
When to use it
in accounts where several people edit questionnaires and nobody remembers who rewrote a question.
Use cases
a change log that dates every creation and every update, useful for explaining why two survey waves do not produce the same numbers.
04Collector EventsA collector is the channel a survey reaches people through, and three events follow its life: collector_created when a collector is created, collector_updated when it is updated, collector_deleted when it is deleted. They answer a different question from the response events, not what people replied but which way the survey went out.

A collector is the channel a survey reaches people through, and three events follow its life: collector_created when a collector is created, collector_updated when it is updated, collector_deleted when it is deleted. They answer a different question from the response events, not what people replied but which way the survey went out.

Key parameters

  • Collector Names or IDs: the collectors the trigger watches, picked from the list or given as an expression.
  • Survey Name or ID: narrows a collector event down to a single questionnaire.
When to use it
when distribution is spread across several people and a new collector deserves at least a look.
Use cases
an immediate alert when a collector is deleted, so a campaign that stopped collecting answers is not discovered on reporting day.
Need help

Need help automating SurveyMonkey with n8n?

A person reads every message.

FAQ

SurveyMonkey and n8n, the questions that come next

01Is the SurveyMonkey integration free in n8n?
Yes. The SurveyMonkey Trigger ships with n8n, so there is nothing to install and nothing extra to pay on the n8n side, on n8n Cloud as well as on a self-hosted instance running the Community Edition under its Sustainable Use license. A workflow behaves the same way in both cases, which means you can prototype on Cloud and move it to your own server later without touching the trigger. What a SurveyMonkey plan itself costs is a separate matter, and this page does not cover it. The only requirement on the SurveyMonkey side is an account you can register a developer app from.
02What credentials does the SurveyMonkey Trigger need?
Two authentication methods are supported: an API access token or OAuth2. The first asks for an Access Token, a Client ID and a Client Secret, all three copied from Settings > Credentials in the app you registered. The second asks for the Client ID and the Client Secret, plus a redirect URL exchange, and ends with the OAuth connection launched from the n8n credential. Either way the app needs six scopes selected under Settings > Scopes: View Surveys, View Collectors, View Responses, View Response Details, Create/Modify Webhooks and View Webhooks. Without the two webhook ones, the trigger has no right to register itself. A credential is created once in n8n and serves every workflow.
03What are the limits of the SurveyMonkey n8n integration?
The catalogue ships the SurveyMonkey Trigger and its 12 events, and that is the scope of the dedicated node. Any call to the SurveyMonkey API that sits outside that catalogue goes through the HTTP Request node, which reaches any endpoint of the API and reuses the same credential through its predefined authentication. Worth planning for while you design the workflow rather than after. Inside the trigger, two settings decide what you receive: Resolve Data, off by default, leaves you with IDs only, and Only Answers reduces the item to the answers of the form. There is no catch-all event, so one node listens to one event.
04Does the SurveyMonkey Trigger react in real time?
Yes. The trigger works by webhook: SurveyMonkey calls an n8n URL as soon as something happens, instead of n8n asking over and over. n8n registers that URL with SurveyMonkey when you activate the workflow, and each event arrives within seconds, with nothing to schedule. The practical consequence is that a deactivated workflow is not a paused workflow: nothing piles up while it is off. Reactivate it and you receive the new events, not the ones you missed. Test with a real submission on a low-traffic survey before you connect whatever comes next.
05n8n or Make for SurveyMonkey?
It depends on four things. Hosting first: n8n runs on your own server or on n8n Cloud, while Make exists only as a hosted platform. Data control follows from that, since a self-hosted instance keeps survey answers inside your own infrastructure. Cost model next: Make bills per operation, so a survey that emits an event for every started and every completed response does not weigh the same on both sides. Visual logic last, where the two are close and habit decides. On an integration that comes down to a single trigger, what usually settles it is what you plan to connect behind it.
Same platform

Other docs you might need on this stack.

Browse all integrations