Recurly to Apache Iceberg integration
Connect Recurly to Apache Iceberg and automatically sync your finance & accounting data. Weld extracts data from Recurly, loads it into Apache Iceberg, and lets you transform the data using SQL or dbt, no custom scripts required.
- account34 cols
- subscription48 cols
- invoice_line_item52 cols
- invoice46 cols
- plan31 cols
- dunning_campaign9 cols
- Extract
- Load
- Keep in sync
- recurly.accountSynced
- recurly.subscriptionSyncing
- recurly.invoice_line_itemSynced
- recurly.invoiceSynced
- recurly.planSynced
- recurly.dunning_campaignSynced
- Recurly tables
- 41
- fields, typed
- 804
- relationships kept
- 51
- agent context included
- MCP
Trusted by data and AI teams
How to set up Recurly to Apache Iceberg in Weld.
In the app, with the API or an agent.
Why sync Recurly to Apache Iceberg?
Ready for analysis.
Centralizing your Recurly 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 Recurly data directly in Apache Iceberg using SQL or your preferred BI tool.
Financial reporting
Centralize financial data from Recurly in Apache Iceberg for automated financial dashboards and month-end close analysis.
Centralized data warehouse
Bring Recurly 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 Recurly to Apache Iceberg. Connect BI tools like Looker, Metabase, or Power BI.
What data can you sync?
Every Recurly table, keys intact.
Weld syncs the objects the Recurly connector exposes into Apache Iceberg, and you choose which tables and fields to include. The connector's docs list what is available.
- account
- subscription
- invoice_line_item
- invoice
- plan
- dunning_campaign
- subscription_history
- billing_info
- shipping_address
- coupon_redemption
- invoice_history
- add_on
- coupon
- item
- invoice_line_item_discount
- account_history
- transaction
- shipping_method
- plan_history
- subscription_add_on
- credit_payment
- account_acquisition
- subscription_ramp_interval
- coupon_item
- subscription_coupon_redemption
- account_note
- coupon_plan
- invoice_coupon_redemption
- invoice_subscription
- transaction_subscription
- and 11 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 Recurly context, finds the tables it needs and runs the query in Apache Iceberg.
How many account rows do we have per dunning_campaign? Use our Recurly data in Apache Iceberg.
Reading the Recurly 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 Recurly API, loading only new and updated records to minimize data transfer and warehouse costs.
- Schema handling
- Weld automatically manages schema changes. If Recurly 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.
Common questions.
About Recurly to Apache Iceberg.
Start syncing Recurly to Apache Iceberg.
Set up your Recurly data pipeline in minutes. No credit card required. Free for 14 days.