Paypal to Databricks integration
Connect Paypal to Databricks and automatically sync your finance & accounting data. Weld extracts data from Paypal, loads it into Databricks, and lets you transform the data using SQL or dbt, no custom scripts required.
Source
WarehouseSourcePaypalConnected- dispute47 cols
- subscription45 cols
- dispute_disputed_transaction20 cols
- dispute_evidence16 cols
- dispute_disputed_transaction_item14 cols
- dispute_fund_movement13 cols
- Extract
- Load
- Keep in sync
DestinationDatabricksReady- paypal.disputeSynced
- paypal.subscriptionSyncing
- paypal.dispute_disputed_transactionSynced
- paypal.dispute_evidenceSynced
- paypal.dispute_disputed_transaction_itemSynced
- paypal.dispute_fund_movementSynced
- Paypal tables
- 28
- fields, typed
- 567
- relationships kept
- 10
- agent context included
- MCP
Trusted by data and AI teams
How to set up Paypal to Databricks in Weld.
In the app, with the API or an agent.
New connectionPaypalAuthorisedWhy sync Paypal to Databricks?
Ready for analysis.
Centralizing your Paypal data in Databricks lets you join it with other data sources for cross-platform analytics and deeper insights.
Build reliable dashboards and reports by querying Paypal data directly in Databricks using SQL or your preferred BI tool.
Financial reporting
Centralize financial data from Paypal in Databricks for automated financial dashboards and month-end close analysis.
Centralized data warehouse
Bring Paypal data into Databricks alongside other sources to create a single source of truth for your organization.
Automated reporting
Replace manual exports and spreadsheet-based reporting with automated pipelines from Paypal to Databricks. Connect BI tools like Looker, Metabase, or Power BI.
What data can you sync?
Every Paypal table, keys intact.
Weld syncs the objects the Paypal connector exposes into Databricks, and you choose which tables and fields to include. The connector's docs list what is available.
- dispute
- subscription
- dispute_disputed_transaction
- dispute_evidence
- dispute_disputed_transaction_item
- dispute_fund_movement
- dispute_offer_history
- subscription_cycle_execution
- dispute_supporting_info
- dispute_adjudication
- dispute_message
- dispute_refund_transaction
- transaction
- invoice
- invoice_recipient
- transaction_item_detail
- billing_plan
- invoice_item
- billing_plan_billing_cycle
- balance
- transaction_incentive
- billing_plan_pricing_tier
- invoice_attachment
- invoice_invoicer_phone
- transaction_item_tax_amount
- transaction_item_checkout_option
- invoice_payment_transaction
- invoice_refund_transaction
Ask your agent.
It queries Databricks for you.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Paypal context, finds the tables it needs and runs the query in Databricks.
How many dispute rows do we have per dispute? Use our Paypal data in Databricks.
Reading the Paypal context first, so the query uses the right tables and keys.
Technical considerations.
What to expect.
- Incremental syncing
- Weld uses incremental syncing where supported by the Paypal API, loading only new and updated records to minimize data transfer and warehouse costs.
- Schema handling
- Weld automatically manages schema changes. If Paypal adds new fields, they're detected and added to the corresponding Databricks tables.
- Data freshness
- Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
- Security
- All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
Keep reading.
Guides, docs and schema.
Common questions.
About Paypal to Databricks.
Start syncing Paypal to Databricks.
Set up your Paypal data pipeline in minutes. No credit card required. Free for 14 days.
SourceWarehouse
