DatriseAI-first ETL

Sendgrid Core MySQL

AI-first ETL from Sendgrid Core into MySQL. Governed entities, incremental sync, typed landing tables.

How Datrise loads Sendgrid Core into MySQL

Datrise syncs Sendgrid Core's records, events, and configuration objects into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Sendgrid Core: SaaS or API data source for analytics and warehouse sync.

MySQL: Widely used OSS relational engine (InnoDB).

How Sendgrid Core entities map to MySQL

Sendgrid Core entityMySQL objectNotes
recordssendgrid_core_recordsid PK · custom fields → JSON columns
eventssendgrid_core_eventsDATETIME/TIMESTAMP events
configuration objectssendgrid_core_configuration_objectsid PK · linked to sendgrid_core_records

FAQ

How does Datrise handle Sendgrid Core's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the Sendgrid Core to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Sendgrid Core to MySQL the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.