Source connector

SurveyMonkey connector

SurveyMonkey integration for databases, warehouses and BI tools

Survey creation and response analytics. Datrise captures SurveyMonkey entities such as surveys, questions, responses, collectors, and quotas, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The SurveyMonkey API v3 authenticates with OAuth 2.0, incremental runs key on start_modified_at, and SurveyMonkey caps calls at Draft/Private apps: 120 requests/minute and 500 requests/day; Public App Directory apps: up to 500,000 requests/day; the daily counter resets at 00:00 GMT.

Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `surveymonkey_surveys`) with a schema derived from the SurveyMonkey API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the SurveyMonkey pipeline page, and join the waitlist to get the SurveyMonkey connector (Product analytics) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What SurveyMonkey data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
surveys	surveymonkey_surveys	Upsert by primary key, incremental on updated-at
questions	surveymonkey_questions	Upsert by primary key, incremental on updated-at
responses	surveymonkey_responses	Upsert by primary key, incremental on updated-at
collectors	surveymonkey_collectors	Upsert by primary key, incremental on updated-at
quotas	surveymonkey_quotas	Upsert by primary key, incremental on updated-at

SurveyMonkey API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	SurveyMonkey API v3
Authentication	OAuth 2.0 — Authorization-code OAuth 2.0 flow issuing a bearer access token that SurveyMonkey documents as not currently expiring, though `responses_write` and `surveys_write` scopes require app approval.
Pagination	page — List endpoints take `page`/`per_page` (max 1,000 per page on most list endpoints, max 100 on the responses bulk endpoint) and return `links.next`/`links.last` for continuation.
Rate limit	Draft/Private apps: 120 requests/minute and 500 requests/day; Public App Directory apps: up to 500,000 requests/day; the daily counter resets at 00:00 GMT.
Incremental cursor	start_modified_at — The `/surveys/{id}/responses` endpoints accept `start_modified_at`/`end_modified_at` (and `start_created_at`/`end_created_at`) date-range filters for incremental pulls.
Webhooks	Yes — SurveyMonkey webhooks (response_completed, response_updated, response_deleted, survey_updated, survey_deleted, etc.)
Bulk export	No
Deletes detectable	Yes — The `response_deleted` and `survey_deleted` webhook events fire on removal; there is no documented polling field for deletes, so webhooks (or a full re-pull) are the only mechanism.

Official API reference

What bites when replicating SurveyMonkey

Response `status` comes back as `completed`, `partial`, `overquota`, or `disqualified` rather than a boolean, so a naive `is_complete` filter silently drops partials that many use cases still need.
Draft/Private apps start at just 500 requests/day and 120 requests/minute, and SurveyMonkey begins hard-enforcing limits once an app exceeds them 3 times within a rolling 30-day window.
OAuth authorization codes expire in 5 minutes, and error code `1013` is returned once a user revokes access, which a long-running connector must handle as a re-auth trigger rather than a transient failure.
The bulk responses endpoint caps `per_page` at 100 even though other list endpoints allow up to 1,000, so a connector tuned against `/surveys` pagination will under-fetch if reused unmodified against `/responses/bulk`.

Compare this against every other documented API

Popular destinations for SurveyMonkey

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

SurveyMonkey connector FAQ

What SurveyMonkey data does the connector extract?: 5 objects: surveys, questions, responses, collectors and quotas. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the SurveyMonkey integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load SurveyMonkey data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each SurveyMonkey → destination pair has its own page with the object-to-table mapping.

Related Product analytics sources

Other sources in the same category, each with its own connector page.

Early access

Launch your SurveyMonkey pipeline with guided onboarding

Join the waitlist to get priority access for SurveyMonkey integrations with guided setup, schema-aware mapping, and production-grade incremental sync.