Recurly Connector

Recurly is a subscription management platform designed to optimize and simplify the process of handling recurring payments and billing cycles.

Start for free View documentation

4.8 on G2

Weld · Data Sources

Recurly

RecurlyYour warehouseLive

account34 columnsSynced

subscription48 columnsSynced

invoice_line_item52 columnsSynced

invoice46 columnsSyncing

plan31 columnsQueued

Lands in

snowflake

bigquery

databricks

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

Recurly

Recurly

Data source

Authenticating...

Ready to connect

Overview

Recurly in your warehouse.
Ready for your agents.

Recurly is a subscription management platform designed to optimize and simplify the process of handling recurring payments and billing cycles. Weld's Recurly connector is fully managed: it extracts data from Recurly, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

Recurly data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Recurly is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 41
fields: 804
relationships: 51

Loading diagram…

invoice_line_item

dunning_campaign

account_acquisition

dunning_campaign_id

parent_account_id

hosted_login_token

has_live_subscription

has_active_subscription

has_future_subscription

has_canceled_subscription

has_paused_subscription

address_street1

address_street2

shipping_address

billing_info_id

shipping_address_id

shipping_method_id

active_invoice_id

shipping_amount

current_period_started_at

current_period_ends_at

current_term_started_at

current_term_ends_at

subscription_coupon_redemption

subscription_ramp_interval

subscription_id

starting_billing_cycle

remaining_billing_cycles

subscription_add_on

subscription_id

unit_amount_decimal

revenue_schedule_type

usage_timeframe

usage_percentage

subscription_add_on_tier

subscription_add_on_id

ending_quantity

unit_amount_decimal

subscription_add_on_percentage_tier

subscription_add_on_id

usage_percentage

billing_info_id

dunning_campaign_id

shipping_address_id

previous_invoice_id

collection_method

invoice_subscription

subscription_id

invoice_coupon_redemption

coupon_redemption_id

invoice_line_item

subscription_id

shipping_address_id

bill_for_account_id

previous_line_item_id

original_line_item_invoice_id

revenue_schedule_type

invoice_line_item_discount

coupon_redemption_id

discount_amount

original_transaction_id

voiced_by_invoice_id

transaction_subscription

subscription_id

parent_invoice_id

applied_to_invoice_id

original_invoice_id

original_credit_payment_id

refund_transaction_id

dunning_campaign_id

interval_length

plan_ramp_interval

starting_billing_cycle

measured_unit_id

usage_percentage

accounting_code

unit_amount_decimal

add_on_percentage_tier

usage_percentage

ending_quantity

unit_amount_decimal

accounting_code

revenue_schedule_type

avalara_transaction_type

max_redemptions

max_redemptions_per_account

unique_coupon_codes_count

unique_code_template

unique_coupon_code_id

coupon_discount_pricing

coupon_redemption

subscription_id

remaining_duration_type

remaining_duration_expires_at

remaining_duration_redemptions_remaining

dunning_campaign

default_campaign

dunning_campaign_id

applies_to_manual_trial

first_communication_interval

send_immediately_on_hard_decline

expire_subscription

total_dunning_days

dunning_cycle_interval

dunning_campaign_id

shipping_method

shipping_method_id

accounting_code

account_history

dunning_campaign_id

billing_info_id

parent_account_id

hosted_login_token

has_live_subscription

has_active_subscription

has_future_subscription

has_canceled_subscription

has_paused_subscription

subscription_history

billing_info_id

shipping_address_id

shipping_method_id

active_invoice_id

shipping_amount

current_period_started_at

current_period_ends_at

current_term_started_at

current_term_ends_at

invoice_history

billing_info_id

dunning_campaign_id

shipping_address_id

previous_invoice_id

collection_method

dunning_campaign_id

interval_length

Open the schema explorer Open the full schema explorer

Weld MCP server

Ask your agent.
It already knows Recurly.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Recurly context, finds the tables it needs and queries your warehouse.

Agent contextRecurly tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextRecurlytables41fields804joins51

>

How many account rows do we have per dunning_campaign? Use our Recurly data.

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 your warehouse

>Ask about your Recurly dataMCP

Destinations

Load Recurly into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Recurly setup guide

Step-by-step instructions to configure and start syncing.

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Recurly connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a Recurly ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "recurly",
    "destination_schema_name": "recurly_data",
    "sync_interval": "0 * * * *"
  }'
▌

FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Put your Recurly data to work.

Connect Recurly, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

Recurly

Source

Weld

MCPAgents

Start for free Talk to us

Connectors

Explore more connectors.
300+ and counting.

View all connectors