Chargebee to Apache Iceberg integration
Connect Chargebee to Apache Iceberg and automatically sync your finance & accounting data. Weld extracts data from Chargebee, loads it into Apache Iceberg, and lets you transform the data using SQL or dbt, no custom scripts required.
- customer68 cols
- subscription77 cols
- invoice45 cols
- item_price32 cols
- transaction38 cols
- order49 cols
- Extract
- Load
- Keep in sync
- chargebee.customerSynced
- chargebee.subscriptionSyncing
- chargebee.invoiceSynced
- chargebee.item_priceSynced
- chargebee.transactionSynced
- chargebee.orderSynced
- Chargebee tables
- 49
- fields, typed
- 804
- relationships kept
- 35
- agent context included
- MCP
Trusted by data and AI teams
How to set up Chargebee to Apache Iceberg in Weld.
In the app, with the API or an agent.
Why sync Chargebee to Apache Iceberg?
Ready for analysis.
Centralizing your Chargebee data in Apache Iceberg lets you join it with other data sources for cross-platform analytics and deeper insights.
Build reliable dashboards and reports by querying Chargebee data directly in Apache Iceberg using SQL or your preferred BI tool.
Financial reporting
Centralize financial data from Chargebee in Apache Iceberg for automated financial dashboards and month-end close analysis.
Centralized data warehouse
Bring Chargebee data into Apache Iceberg 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 Chargebee to Apache Iceberg. Connect BI tools like Looker, Metabase, or Power BI.
What data can you sync?
Every Chargebee table, keys intact.
Weld syncs the objects the Chargebee connector exposes into Apache Iceberg, and you choose which tables and fields to include. The connector's docs list what is available.
- customer
- subscription
- invoice
- item_price
- transaction
- order
- payment_source
- credit_note
- item
- credit_note_line_item
- unbilled_charge
- usage
- item_family
- coupon
- order_line_item
- invoice_line_item
- virtual_bank_account
- subscription_item
- promotional_credit
- allocated_invoice
- transaction_invoice
- subscription_item_tier
- subscription_coupon
- credit_note_allocation
- payment_source_mandate
- credit_note_refund
- credit_note_line_item_tax
- invoice_line_item_tax
- order_line_item_tax
- subscription_contract_term
- and 19 more
Ask your agent.
It queries Apache Iceberg for you.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Chargebee context, finds the tables it needs and runs the query in Apache Iceberg.
How many subscription rows do we have per customer? Use our Chargebee data in Apache Iceberg.
Reading the Chargebee 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 Chargebee API, loading only new and updated records to minimize data transfer and warehouse costs.
- Schema handling
- Weld automatically manages schema changes. If Chargebee adds new fields, they're detected and added to the corresponding Apache Iceberg 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.
Chargebee setup guide
How to connect Chargebee to Weld, step by step.
DocumentationApache Iceberg setup guide
How to connect Apache Iceberg to Weld, step by step.
SchemaChargebee schema explorer
Browse all 49 tables and 804 fields.
ConnectorChargebee connector
Everything Weld does with Chargebee.
Common questions.
About Chargebee to Apache Iceberg.
Start syncing Chargebee to Apache Iceberg.
Set up your Chargebee data pipeline in minutes. No credit card required. Free for 14 days.