PayPal Transactions to Domo Integration

How Datrise loads PayPal Transactions into Domo

Datrise syncs PayPal Transactions's transactions, payers, balances, fees, refunds, and currency conversions into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

PayPal Transactions: PayPal transaction history and settlement detail.

Domo: Cloud BI platform combining data integration and executive dashboards.

How PayPal Transactions entities map to Domo

PayPal Transactions entity	Domo object	Notes
transactions	`paypal_transaction_transactions`	id PK · custom fields → flattened columns for Magic ETL
payers	`paypal_transaction_payers`	id PK · linked to paypal_transaction_transactions
balances	`paypal_transaction_balances`	id PK · linked to paypal_transaction_transactions
fees	`paypal_transaction_fees`	id PK · linked to paypal_transaction_transactions

FAQ

How does Datrise handle PayPal Transactions's custom fields in Domo?

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

How does the PayPal Transactions to Domo sync stay up to date?

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

Connect PayPal Transactions to Domo 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.