Real-time
Two-way sync
Changes in Kommo or Recurly instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Kommo to Recurly integration — real-time, two-way sync
Keep Kommo 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 Kommo and Recurly
Sync customers, invoices, and payment status between Recurly and Kommo in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Kommo 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 Plans, Invoices, Transactions, Line Items in Recurly to Contacts, Companies, Pipelines & Statuses, Tasks in Kommo 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 Keep customer records consistent between Kommo and invoicing or ERP systems
- 04 Mirror pipeline stage changes into BI tools for forecasting
Common sync patterns
Payment status on the account
Invoice and payment status from Recurly appears on the account in Kommo, so reps see overdue balances before they promise the next order.
Billing detail changes flow back
When a contact or address is corrected in Kommo, Recurly gets the update before the next invoice goes out.
Collections with context
Finance sees the account owner and relationship history from Kommo when chasing a balance, and sales sees that the chase is happening.
What you can sync between Kommo 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.
| Kommo objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Follow-up records keep rep activity consistent across systems. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Tasks is specific to Kommo and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Notes Free-text and system notes attach context to synced leads and contacts. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Notes is specific to Kommo and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Custom Fields is specific to Kommo and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Users Account users map lead ownership to people in other systems. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Users is specific to Kommo and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Chats is specific to Kommo and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. | |
| Leads The central pipeline record; external signups and form fills sync in as leads. | 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). | Leads is specific to Kommo and Billing Info to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Kommo 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.
Kommo Recurly Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Kommo 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 Kommo through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kommo: Subject to per-account request 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 Kommo ⇄ Recurly
Connect Kommo and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kommo 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 Kommo or Recurly record.
Observability
Monitoring
Track your Kommo ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Kommo and Recurly.
How the Kommo and Recurly connectors work
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request 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 Kommo 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 Kommo 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.
Kommo
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kommo 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 · Kommo ⇄ 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.
Kommo RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kommo and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kommo and Recurly: authenticate both systems, choose the objects to sync (such as Kommo's Tasks and Notes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Kommo: Webhooks on record add and update events, plus polling for backfill. 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: Plans, Invoices, Transactions, Line Items, plus custom fields where Recurly exposes them. On the Kommo side: Contacts, Companies, Pipelines & Statuses, Tasks. 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 Kommo and Recurly: Payment status on the account; Billing detail changes flow back; Collections with context. Invoice and payment status from Recurly appears on the account in Kommo, so reps see overdue balances before they promise the next order.
-
Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Recurly: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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 513 integrations available for Kommo and Recurly.
Popular · 7 of 513
-
Kommo ⇄ Logisense -
Kommo ⇄ Bill -
Kommo ⇄ Braintree -
Kommo ⇄ Navan -
Recurly ⇄ Zoho CRM -
Recurly ⇄ Shopify -
Recurly ⇄ Affinity
No integrations match .
