Source connector

Zapier connector

Zapier integration for databases, warehouses and BI tools

Automation runs connecting apps through triggers. Datrise captures Zapier entities such as zaps, task runs, triggers, actions, connected apps and run statuses, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Zapier Platform (Workflow/Embed API for triggers) + Storage by Zapier REST API authenticates with API key, and Zapier caps calls at Workflow/Embed API: 60 requests/minute per IP address, or 150 requests/minute for Partner accounts, whichever is hit first.

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 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 `zapier_zaps`) with a schema derived from the Zapier 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 Zapier pipeline page, and join the waitlist to get the Zapier connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Zapier 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
zaps	zapier_zaps	Upsert by primary key, incremental on updated-at
task runs	zapier_task_runs	Append-only, incremental by timestamp
triggers	zapier_triggers	Upsert by primary key, incremental on updated-at
actions	zapier_actions	Upsert by primary key, incremental on updated-at
connected apps	zapier_connected_apps	Upsert by primary key, incremental on updated-at
run statuses	zapier_run_statuses	Append-only, incremental by timestamp

Zapier API: setup facts for the connector

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

API	Zapier Platform (Workflow/Embed API for triggers) + Storage by Zapier REST API
Authentication	API key — Storage by Zapier is authenticated purely by a client-supplied `secret` (must be UUID4-formatted) passed as a query parameter, not a per-user OAuth token.
Pagination	none — `GET https://store.zapier.com/api/records` returns the full set of records for a given secret in one response; there is no cursor or page parameter documented.
Rate limit	Workflow/Embed API: 60 requests/minute per IP address, or 150 requests/minute for Partner accounts, whichever is hit first
Incremental cursor	Not published
Webhooks	Yes — REST Hook triggers (per-Zap subscribe/unsubscribe URLs, with an `X-Hook-Secret` handshake for endpoint verification)
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Zapier

Storage by Zapier caps each store secret at 500 keys and 1 MB (1,000,000 bytes) per value, and silently deletes keys after 2 months of inactivity.
The store `secret` must be UUID4-formatted; Zapier stopped allowing arbitrary plain-text secrets in August 2020, breaking older integrations that hardcoded a simple key.
Polling triggers only re-check a customer's app every 1 to 15 minutes depending on that customer's Zapier plan, so treating Zapier as a real-time source overstates its actual freshness.
The Workflow/Embed API enforces a hard 60 requests/minute per IP (150/minute for Partner accounts); exceeding it returns HTTP `429` with a fixed 60-second cooldown, not a variable backoff window.

Compare this against every other documented API

Popular destinations for Zapier

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

Zapier connector FAQ

What Zapier data does the connector extract?: 6 objects: zaps, task runs, triggers, actions, connected apps and run statuses. Each lands in its own table with types preserved; history-style objects (2: task runs and run statuses) load as append-only streams.
Is the Zapier 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 Zapier data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Zapier → destination pair has its own page with the object-to-table mapping.

Related sources

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

Early access

Launch your Zapier pipeline with guided onboarding

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