Real-time
Two-way sync
Changes in Close or Recurly instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Close to Recurly integration — real-time, two-way sync
Keep Close and Recurly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Close and Recurly
Sync customers, invoices, and payment status between Recurly and Close in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Close knows the relationship: who the contacts are and what is in motion with the account. Recurly knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Billing Info, Measured Units and Usage, Accounts, Subscriptions in Recurly to Smart Views, Leads, Contacts, Opportunities in Close with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
Common use cases
- 01 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
- 02 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
- 03 Write product usage or firmographic data from an internal database onto Close lead custom fields to prioritize follow-up.
- 04 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
Common sync patterns
Billing detail changes flow back
When a contact or address is corrected in Close, Recurly gets the update before the next invoice goes out.
Collections with context
Finance sees the account owner and relationship history from Close when chasing a balance, and sales sees that the chase is happening.
Where Close tracks deals: closed-won creates the finance record
A won opportunity creates or updates the customer in Recurly with the right billing details, so invoicing starts without re-keying.
What you can sync between Close and Recurly
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Close objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Follow-up items assigned to users; synced for workload and SLA reporting. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Tasks is specific to Close and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. | |
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). | Custom Activities is specific to Close and Billing Info to Recurly — each maps to any object or custom field on the other side. | |
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Custom Fields is specific to Close and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. | Users is specific to Close and Accounts to Recurly — each maps to any object or custom field on the other side. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. | Smart Views is specific to Close and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Leads is specific to Close and Plans to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Close and Recurly
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Close Recurly Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Close Sub-second propagation
DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.
DeliveryEach detected change is written to Close through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Close: Subject to per-endpoint rate limits communicated in response headers.
- Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Close ⇄ Recurly
Connect Close and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Close or Recurly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Close or Recurly record.
Observability
Monitoring
Track your Close ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Close and Recurly.
How the Close and Recurly connectors work
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
Recurly
- Integration surface
- REST API (V3, date-versioned; legacy V2 XML API also exists)
- Authentication
- API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
- Change detection
- Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
- Capabilities
- read · write · webhooks
- Rate limits
- Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works
How to connect Close to Recurly — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Close and Recurly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Close
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Close and Recurly objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Close ⇄ RecurlyCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Close RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Close and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Close and Recurly: authenticate both systems, choose the objects to sync (such as Close's Tasks and Custom Activities), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Close and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Close and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Close: Webhook subscriptions for record events, with polling on date_updated fields for backfills. On Recurly: Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Billing Info, Measured Units and Usage, Accounts, Subscriptions, plus custom fields where Recurly exposes them. On the Close side: Smart Views, Leads, Contacts, Opportunities. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 524 integrations available for Close and Recurly.
Popular · 7 of 524
-
Close ⇄ Navan -
Close ⇄ Ramp -
Close ⇄ Rillet -
Recurly ⇄ Vitally -
Recurly ⇄ DealCloud -
Recurly ⇄ Chorusai -
Recurly ⇄ Clari
No integrations match .
