Real-time
Two-way sync
Changes in Insightly or Recurly instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Insightly to Recurly integration — real-time, two-way sync
Keep Insightly 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 Insightly and Recurly
Sync customers, invoices, and payment status between Recurly and Insightly in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Insightly 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 Subscriptions, Plans, Invoices, Transactions in Recurly to Contacts, Organizations, Leads, Opportunities in Insightly 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 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.
- 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 03 Two-way sync of Insightly contacts and organizations with a marketing automation platform
- 04 Replicate opportunities into Postgres or a warehouse so RevOps can report on pipeline with SQL
Common sync patterns
Collections with context
Finance sees the account owner and relationship history from Insightly when chasing a balance, and sales sees that the chase is happening.
Where Insightly 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 Insightly, so reps see overdue balances before they promise the next order.
What you can sync between Insightly 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.
| Insightly objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Notes Free-text context attaches to synced records for downstream visibility. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Notes is specific to Insightly and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Products Product catalog entries support line-item syncing on opportunities and quotes. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Products is specific to Insightly and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Custom Fields Per-object custom fields carry enrichment and billing data written from external systems. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Custom Fields is specific to Insightly and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. | |
| Contacts Person records sync with marketing and support tools to keep one contact list. | 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). | Contacts is specific to Insightly and Billing Info to Recurly — each maps to any object or custom field on the other side. | |
| Organizations Company records map to accounts in ERPs and other CRMs. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Organizations is specific to Insightly and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects sync in from forms and enrichment sources before conversion. | 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. | Leads is specific to Insightly and Accounts to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Insightly 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.
Insightly Recurly Interval-based propagation
DetectionStacksync polls Insightly for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record updated-date fields.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Insightly 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 Insightly through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Insightly: Daily API request caps vary by Insightly plan.
- 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 Insightly ⇄ Recurly
Connect Insightly and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Insightly–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Insightly 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 Insightly or Recurly record.
Observability
Monitoring
Track your Insightly ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Insightly and Recurly.
How the Insightly and Recurly connectors work
Insightly
- Integration surface
- REST API (versioned)
- Authentication
- API key sent via HTTP Basic authentication
- Change detection
- Polling on record updated-date fields
- Capabilities
- read · write
- Rate limits
- Daily API request caps vary by Insightly plan
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 Insightly 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 Insightly 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.
Insightly
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Insightly 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 · Insightly ⇄ 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.
Insightly RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Insightly and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Insightly and Recurly: authenticate both systems, choose the objects to sync (such as Insightly's Notes and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Insightly and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Insightly: Polling on record updated-date fields. 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: Subscriptions, Plans, Invoices, Transactions, plus custom fields where Recurly exposes them. On the Insightly side: Contacts, Organizations, Leads, 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.
-
Common patterns for Insightly and Recurly: Collections with context; Where Insightly tracks deals: closed-won creates the finance record; Payment status on the account. Finance sees the account owner and relationship history from Insightly when chasing a balance, and sales sees that the chase is happening.
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 511 integrations available for Insightly and Recurly.
Popular · 6 of 511
-
Insightly ⇄ Chargebee -
Insightly ⇄ Hyperline -
Insightly ⇄ Pigment -
Insightly ⇄ QuickBooks -
Recurly ⇄ Affinity -
Recurly ⇄ Apollo.io
No integrations match .
