DatriseAI-first ETL

GoCardless to GoodData Integration

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

How Datrise loads GoCardless into GoodData

Datrise syncs GoCardless's payments, customers, mandates, subscriptions, payouts, and refunds 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

GoCardless: Bank debit collection and recurring payments.

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

How GoCardless entities map to GoodData

GoCardless entityGoodData objectNotes
paymentsgocardless_paymentsid PK · custom fields → flattened columns
customersgocardless_customersid PK · linked to gocardless_payments
mandatesgocardless_mandatesid PK · linked to gocardless_payments
subscriptionsgocardless_subscriptionsid PK · linked to gocardless_payments

FAQ

How does Datrise handle GoCardless'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 GoCardless to GoodData sync stay up to date?

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

Related pipelines

Early access

Connect GoCardless 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.