Paypal to Google BigQuery integration
Connect Paypal to Google BigQuery and automatically sync your finance & accounting data. Weld extracts data from Paypal, loads it into Google BigQuery, 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
DestinationGoogle BigQueryReady- 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 Google BigQuery in Weld.
In the app, with the API or an agent.
New connectionPaypalAuthorisedWhy sync Paypal to Google BigQuery?
Ready for analysis.
Centralizing your Paypal data in Google BigQuery 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 Google BigQuery using SQL or your preferred BI tool.
Financial reporting
Centralize financial data from Paypal in Google BigQuery for automated financial dashboards and month-end close analysis.
Centralized data warehouse
Bring Paypal data into Google BigQuery 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 Google BigQuery. 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 Google BigQuery, 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 Google BigQuery 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 Google BigQuery.
How many dispute rows do we have per dispute? Use our Paypal data in Google BigQuery.
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 Google BigQuery 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 Google BigQuery.
Start syncing Paypal to Google BigQuery.
Set up your Paypal data pipeline in minutes. No credit card required. Free for 14 days.
SourceWarehouse
