Source connector

Drip connector

Drip integration for databases, warehouses and BI tools

Ecommerce marketing automation and workflows. Datrise captures Drip entities such as subscribers, campaigns, workflows, orders, email events and tags, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Drip REST API v2 (JSON over HTTPS) authenticates with API key, OAuth 2.0, and Drip caps calls at 3,600 individual requests per hour per token; 50 batch requests per hour, each batch carrying up to 1,000 records.

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 `drip_subscribers`) with a schema derived from the Drip 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 Drip pipeline page, and join the waitlist to get the Drip connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Drip 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
subscribers	drip_subscribers	Upsert by primary key, incremental on updated-at
campaigns	drip_campaigns	Upsert by primary key, incremental on updated-at
workflows	drip_workflows	Upsert by primary key, incremental on updated-at
orders	drip_orders	Upsert by primary key, incremental on updated-at
email events	drip_email_events	Append-only, incremental by timestamp
tags	drip_tags	Upsert by primary key, incremental on updated-at

Drip API: setup facts for the connector

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

API	Drip REST API v2 (JSON over HTTPS)
Authentication	API key, OAuth 2.0 — HTTP Basic Auth with the account's API token as the username and a blank password for private integrations; OAuth 2.0 authorization code for third-party (public) apps.
Pagination	page — page / per_page query params; default page size is 100, though some collection endpoints accept per_page up to 1,000. Responses include a meta object with current page, count and total pages.
Rate limit	3,600 individual requests per hour per token; 50 batch requests per hour, each batch carrying up to 1,000 records
Incremental cursor	Not published
Webhooks	Yes — Drip Webhooks (subscriber.created, subscriber.deleted, subscriber.updated_custom_field, email/campaign events, etc.)
Bulk export	Yes — Batches API (create/update up to 1,000 subscribers, events, orders, products or carts per call)
Deletes detectable	Yes — subscriber.deleted webhook event; there is no documented deleted-records list endpoint for reconciling a full sync.

Official API reference

What bites when replicating Drip

Individual endpoints allow 3,600 requests/hour per token, but the separate Batches endpoint is capped far lower at 50 batch calls/hour even though each batch can carry 1,000 records.
There is no updated_since filter on the Subscribers list endpoint, so a full incremental pipeline has to lean on webhooks (e.g. subscriber.updated_email_address) instead of a single 'record changed' timestamp.
Default page size is only 100 even though some endpoints accept per_page up to 1,000 — don't assume one page-size ceiling applies across every list endpoint.
Deleted subscribers surface only through the subscriber.deleted webhook; missing that event means a batch reconciliation has no way to detect the deletion.

Compare this against every other documented API

Popular destinations for Drip

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

Drip connector FAQ

What Drip data does the connector extract?: 6 objects: subscribers, campaigns, workflows, orders, email events and tags. Each lands in its own table with types preserved; history-style objects (1: email events) load as append-only streams.
Is the Drip 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 Drip data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Drip → 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 Drip pipeline with guided onboarding

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