Weld
Start free

Recurly to Azure SQL Database integration

Connect Recurly to Azure SQL Database and automatically sync your finance & accounting data. Weld extracts data from Recurly, loads it into Azure SQL Database, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for freeView setup guide
4.8 on G2
RecurlySource
WeldWeld
Azure SQL DatabaseWarehouse
Weld · New sync
RecurlySourceRecurlyConnected
Tables to sync
  • account34 cols
  • subscription48 cols
  • invoice_line_item52 cols
  • invoice46 cols
  • plan31 cols
  • dunning_campaign9 cols
  • Extract
  • Load
  • Keep in sync
Azure SQL DatabaseDestinationAzure SQL DatabaseReady
recurly schema
  • 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

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Recurly to Azure SQL Database in Weld.
In the app, with the API or an agent.

Setup guideAPI guideMCP docs
Weld · New Recurly sync
RecurlyNew connectionRecurlyAuthorised
Connection namerecurly
AuthorizeOpens Recurly to grant read access
Use cases

Why sync Recurly to Azure SQL Database?
Ready for analysis.

Centralizing your Recurly data in Azure SQL Database 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 Azure SQL Database using SQL or your preferred BI tool.

  • Financial reporting

    Centralize financial data from Recurly in Azure SQL Database for automated financial dashboards and month-end close analysis.

  • Centralized data warehouse

    Bring Recurly data into Azure SQL Database 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 Azure SQL Database. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Recurly table, keys intact.

Weld syncs the objects the Recurly connector exposes into Azure SQL Database, and you choose which tables and fields to include. The connector's docs list what is available.

Open the schema explorer
All 41 tables
  • 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
Weld MCP server

Ask your agent.
It queries Azure SQL Database 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 Azure SQL Database.

Set up the MCP serverClaudeCursorChatGPTGemini
Claude CodeOpus 5
>

How many account rows do we have per dunning_campaign? Use our Recurly data in Azure SQL Database.

Reading the Recurly context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.recurly.account
raw.recurly.dunning_campaign
+ 39 more Recurly tables
●weld·get_reference_schema
⎿account · 34 columns
joins dunning_campaign on dunning_campaign_id
●weld·run_query
⎿select d.id, count(*) from {{raw.recurly.account}} a
join {{raw.recurly.dunning_campaign}} d on a.dunning_campaign_id = d.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Recurly data in Azure SQL Database
>Ask about your Recurly data
Under the hood

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 Azure SQL Database 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.
Resources

Keep reading.
Guides, docs and schema.

Documentation

Recurly setup guide

How to connect Recurly to Weld, step by step.

Documentation

Azure SQL Database setup guide

How to connect Azure SQL Database to Weld, step by step.

Schema

Recurly schema explorer

Browse all 41 tables and 804 fields.

Connector

Recurly connector

Everything Weld does with Recurly.

FAQ

Common questions.
About Recurly to Azure SQL Database.

Start syncing Recurly to Azure SQL Database.

Set up your Recurly data pipeline in minutes. No credit card required. Free for 14 days.

RecurlySource
WeldWeld
Azure SQL DatabaseWarehouse
Start for freeTalk to us
Related

Related integrations.
More with Recurly and Azure SQL Database.

View all