GoCardless to Amazon QuickSight Integration

How Datrise loads GoCardless into Amazon QuickSight

Datrise syncs GoCardless's payments, customers, mandates, subscriptions, payouts, and refunds into Amazon QuickSight as warehouse tables or a SPICE-loaded dataset. Flexible or custom fields land in flattened columns for analyses, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind SPICE or direct query, so re-runs update only what changed. Date-partitioned facts to bound SPICE refresh. QuickSight SPICE is an in-memory copy, so Datrise keeps the backing tables incremental so refreshes stay cheap.

Ideal for AWS-native dashboards with pay-per-session pricing.

Endpoints

GoCardless: Bank debit collection and recurring payments.

Amazon QuickSight: AWS serverless BI with SPICE and embedded analytics.

How GoCardless entities map to Amazon QuickSight

GoCardless entity	Amazon QuickSight object	Notes
payments	`gocardless_payments`	id PK · custom fields → flattened columns for analyses
customers	`gocardless_customers`	id PK · linked to gocardless_payments
mandates	`gocardless_mandates`	id PK · linked to gocardless_payments
subscriptions	`gocardless_subscriptions`	id PK · linked to gocardless_payments

FAQ

How does Datrise handle GoCardless's custom fields in Amazon QuickSight?

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

How does the GoCardless to Amazon QuickSight sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind SPICE or direct query.

Related pipelines

Early access

Connect GoCardless to Amazon QuickSight 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.