Source connector

SendGrid connector

SendGrid integration for databases, warehouses and BI tools

Transactional and marketing email delivery platform. Datrise captures SendGrid entities such as messages, templates, suppressions, bounces, and engagement events, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The SendGrid Web API v3 (Marketing Campaigns + Event Webhook) authenticates with API key, incremental runs key on updated_at (via SGQL query on POST /v3/marketing/contacts/search).

Of the 5 objects, 3 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 `sendgrid_messages`) with a schema derived from the SendGrid 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 SendGrid pipeline page, and join the waitlist to get the SendGrid connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What SendGrid 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
messages	sendgrid_messages	Append-only, incremental by timestamp
templates	sendgrid_templates	Upsert by primary key, incremental on updated-at
suppressions	sendgrid_suppressions	Upsert by primary key, incremental on updated-at
bounces	sendgrid_bounces	Upsert by primary key, incremental on updated-at
engagement events	sendgrid_engagement_events	Append-only, incremental by timestamp

SendGrid API: setup facts for the connector

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

API	SendGrid Web API v3 (Marketing Campaigns + Event Webhook)
Authentication	API key — Every request carries `Authorization: Bearer <API_KEY>`; API keys can be scoped to specific permission areas of the account rather than granted full access.
Pagination	offset — Most v3 list endpoints use `limit`/`offset` query params; the Marketing Contacts Search endpoint (`POST /v3/marketing/contacts/search`) is not paginated at all and simply returns at most 50 matches.
Rate limit	Not published
Incremental cursor	updated_at (via SGQL query on POST /v3/marketing/contacts/search) — `created_at`/`updated_at` are returned as ISO 8601 strings; the older Unix-timestamp format for these fields is deprecated.
Webhooks	Yes — Event Webhook
Bulk export	Yes — Marketing Contacts Export (POST /v3/marketing/contacts/exports)
Deletes detectable	No — There is no documented tombstone or deleted flag for removed Marketing Contacts; suppression lists (bounces, unsubscribes, spam reports) are separate, additive resources and do not represent contact deletion

Official API reference

What bites when replicating SendGrid

Search Contacts caps results at 50 records per query regardless of how many rows match, and any query running longer than 20 seconds returns HTTP 408, so bulk extraction cannot rely on this endpoint alone.
Rate limits are set per endpoint, not account-wide, with no single published number; only response headers `X-RateLimit-Limit`/`X-RateLimit-Remaining`/`X-RateLimit-Reset` reveal each endpoint's actual budget.
Marketing Contacts Export is asynchronous — `POST /v3/marketing/contacts/exports` returns HTTP 202 with a job id that must be polled — and defaults to a 5000 MB `max_file_size` per output file, splitting large exports across multiple files above that size.
The Event Webhook documents no retry policy for ordinary delivery failures (only an OAuth-token-refresh retry is documented), so a receiving endpoint that is briefly unavailable can permanently lose those events.

Compare this against every other documented API

Popular destinations for SendGrid

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

SendGrid connector FAQ

What SendGrid data does the connector extract?: 5 objects: messages, templates, suppressions, bounces and engagement events. Each lands in its own table with types preserved; history-style objects (2: messages and engagement events) load as append-only streams.
Is the SendGrid 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 SendGrid data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each SendGrid → 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 SendGrid pipeline with guided onboarding

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