Source connector

GetResponse connector

GetResponse integration for databases, warehouses and BI tools

Email marketing with funnels, webinars, and automations. Datrise captures GetResponse entities such as contacts, campaigns, autoresponders, funnels, webinars and email events, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The GetResponse API v3 authenticates with API key, OAuth 2.0, incremental runs key on createdOn, and GetResponse caps calls at 30,000 API calls per rolling 10-minute window and 80 calls per second per account, with a maximum of 10 simultaneous requests.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 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 `getresponse_contacts`) with a schema derived from the GetResponse 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 GetResponse pipeline page, and join the waitlist to get the GetResponse connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What GetResponse 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
contacts	getresponse_contacts	Upsert by primary key, incremental on updated-at
campaigns	getresponse_campaigns	Upsert by primary key, incremental on updated-at
autoresponders	getresponse_autoresponders	Upsert by primary key, incremental on updated-at
funnels	getresponse_funnels	Upsert by primary key, incremental on updated-at
webinars	getresponse_webinars	Upsert by primary key, incremental on updated-at
email events	getresponse_email_events	Append-only, incremental by timestamp

GetResponse API: setup facts for the connector

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

API	GetResponse API v3
Authentication	API key, OAuth 2.0 — Primary auth is a static key sent as `X-Auth-Token: api-key <key>` (unused keys expire after 90 days); OAuth 2.0 Authorization Code, Client Credentials, Implicit, and Refresh Token flows are also supported via a Bearer token.
Pagination	page — List endpoints such as `/v3/contacts` take `page` and `perPage` query params, returning 100 results per page by default (up to 1,000).
Rate limit	30,000 API calls per rolling 10-minute window and 80 calls per second per account, with a maximum of 10 simultaneous requests
Incremental cursor	createdOn — Contacts can be sorted with `sort[createdOn]=ASC` and paged forward by creation time, but there is no documented `updatedOn`/changed-since filter, so in-place edits to existing contacts are not cursorable.
Webhooks	Yes — Webhooks (contact subscribed/unsubscribed, custom field changed, link clicked, etc.)
Bulk export	No
Deletes detectable	Yes — Contacts carry a `deletedOn` timestamp field (null while active, set once removed or unsubscribed) alongside a `reason` field explaining the removal.

Official API reference

What bites when replicating GetResponse

The `X-Auth-Token` API key silently expires after 90 days of no use, so a dormant connector's next sync fails auth rather than data extraction.
The rolling window caps requests at 30,000 per 10 minutes and 80 per second with only 10 concurrent connections, well below the volume a full-catalog contacts backfill can generate without pacing.
There is no `updatedOn`/changed-since query parameter on `/v3/contacts`, so incremental sync can only order by `createdOn` and must re-poll for edits to previously synced contacts.
GetResponse MAX accounts must add an `X-Domain` header to every request; omitting it on a MAX account returns errors that look like an auth failure.

Compare this against every other documented API

Popular destinations for GetResponse

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

GetResponse connector FAQ

What GetResponse data does the connector extract?: 6 objects: contacts, campaigns, autoresponders, funnels, webinars and email events. Each lands in its own table with types preserved; history-style objects (1: email events) load as append-only streams.
Is the GetResponse 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 GetResponse data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each GetResponse → destination pair has its own page with the object-to-table mapping.

Related Marketing sources

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

Early access

Launch your GetResponse pipeline with guided onboarding

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