Real-time
Two-way sync
Changes in Nutshell or Recurly instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Nutshell to Recurly integration — real-time, two-way sync
Keep Nutshell 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 Nutshell and Recurly
Sync customers, invoices, and payment status between Recurly and Nutshell in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Nutshell 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 Measured Units and Usage, Accounts, Subscriptions, Plans in Recurly to Users, Leads, People, Companies in Nutshell 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 Push closed-won leads to accounting software to trigger invoicing automatically.
- 04 Keep People and Companies consistent between Nutshell and email marketing or outreach tools.
Common sync patterns
Where Nutshell 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.
Payment status on the account
Invoice and payment status from Recurly appears on the account in Nutshell, so reps see overdue balances before they promise the next order.
Billing detail changes flow back
When a contact or address is corrected in Nutshell, Recurly gets the update before the next invoice goes out.
What you can sync between Nutshell 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.
| Nutshell objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Companies Account records that group people and leads for account-level syncs | 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. | Companies is specific to Nutshell and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Activities Logged calls, meetings, and emails used for engagement reporting | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Activities is specific to Nutshell and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Tasks Rep to-dos mirrored into external work-management or reporting systems | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Tasks is specific to Nutshell and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Notes Free-text history attached to leads and contacts, replicated for a full timeline | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Notes is specific to Nutshell and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Products Line items attached to leads, used to sync sold products into billing | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Products is specific to Nutshell and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Tags Segmentation labels mapped to lists or filters in downstream tools | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Tags is specific to Nutshell and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Nutshell 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.
Nutshell Recurly Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Nutshell 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Nutshell: Subject to the platform's API rate limits.
- 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 Nutshell ⇄ Recurly
Connect Nutshell and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Nutshell 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 Nutshell or Recurly record.
Observability
Monitoring
Track your Nutshell ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Nutshell and Recurly.
How the Nutshell and Recurly connectors work
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's API rate limits
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 Nutshell 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 Nutshell 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.
Nutshell
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Nutshell 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 · Nutshell ⇄ 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.
Nutshell RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Nutshell and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Nutshell and Recurly: authenticate both systems, choose the objects to sync (such as Nutshell's Companies and Activities), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Nutshell and Recurly records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Nutshell and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Nutshell–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Nutshell and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Nutshell: Webhook subscriptions for record events, with polling as fallback. 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: Measured Units and Usage, Accounts, Subscriptions, Plans, plus custom fields where Recurly exposes them. On the Nutshell side: Users, Leads, People, Companies. Stacksync auto-detects both schemas and converts types between the two systems.
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 415 integrations available for Nutshell and Recurly.
Popular · 7 of 415
-
Nutshell ⇄ Stripe -
Nutshell ⇄ Coupa -
Nutshell ⇄ Zuora -
Nutshell ⇄ Adyen -
Recurly ⇄ DealCloud -
Recurly ⇄ Chorusai -
Recurly ⇄ Clari
No integrations match .
