Real-time
Two-way sync
Changes in Intercom or Recurly instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Intercom to Recurly integration — real-time, two-way sync
Keep Intercom 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 Intercom and Recurly
Sync customers, invoices, and payment status between Recurly and Intercom in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Intercom 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 Tickets, Data Events, Custom Data Attributes, Tags in Intercom 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 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- 04 Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
Common sync patterns
Collections with context
Finance sees the account owner and relationship history from Intercom when chasing a balance, and sales sees that the chase is happening.
Where Intercom 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 Intercom, so reps see overdue balances before they promise the next order.
What you can sync between Intercom 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.
| Intercom objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | 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 Data Attributes is specific to Intercom and Billing Info to Recurly — each maps to any object or custom field on the other side. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Tags is specific to Intercom and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | 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. | Segments is specific to Intercom and Accounts to Recurly — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | 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. | Admins & Teams is specific to Intercom and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Articles Help center content is accessible via API for knowledge sync and audits. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Articles is specific to Intercom and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Contacts is specific to Intercom and Invoices to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Intercom 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.
Intercom Recurly Sub-second propagation
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Intercom 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 Intercom through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Intercom: Subject to per-app rate limits on the Intercom API.
- 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 Intercom ⇄ Recurly
Connect Intercom and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Intercom 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 Intercom or Recurly record.
Observability
Monitoring
Track your Intercom ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Intercom and Recurly.
How the Intercom and Recurly connectors work
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
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 Intercom 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 Intercom 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.
Intercom
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Intercom 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 · Intercom ⇄ 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.
Intercom RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Intercom and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Recurly: authenticate both systems, choose the objects to sync (such as Intercom's Custom Data Attributes and Tags), 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 Intercom and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Intercom and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Intercom: Webhook topic subscriptions for contact, company, and conversation 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: Subscriptions, Plans, Invoices, Transactions, plus custom fields where Recurly exposes them. On the Intercom side: Tickets, Data Events, Custom Data Attributes, Tags. 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 508 integrations available for Intercom and Recurly.
Popular · 7 of 508
-
Intercom ⇄ Zuora -
Intercom ⇄ Adyen -
Intercom ⇄ Logisense -
Intercom ⇄ Bill -
Recurly ⇄ Copper CRM -
Recurly ⇄ Creatio CRM -
Recurly ⇄ Folk CRM
No integrations match .
