DatriseAI-first ETL

SendGrid to GoodData Integration

AI-first ETL from SendGrid into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads SendGrid into GoodData

Datrise syncs SendGrid's messages, contacts, delivery events, bounces, opens, and marketing campaigns into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

SendGrid: Transactional email delivery and engagement events.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How SendGrid entities map to GoodData

SendGrid entityGoodData objectNotes
messagessendgrid_core_messagesid PK · custom fields → flattened columns
contactssendgrid_core_contactsid PK · linked to sendgrid_core_messages
delivery eventssendgrid_core_delivery_eventsdate dimensions events
bouncessendgrid_core_bouncesid PK · linked to sendgrid_core_messages

FAQ

How does Datrise handle SendGrid's custom fields in GoodData?

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

How does the SendGrid to GoodData sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect SendGrid to GoodData 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.