Real-time
Two-way sync
Changes in Folk CRM or Recurly instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Folk CRM to Recurly integration — real-time, two-way sync
Keep Folk CRM 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 Folk CRM and Recurly
Sync customers, invoices, and payment status between Recurly and Folk CRM in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Folk CRM 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 Accounts, Subscriptions, Plans, Invoices in Recurly to People, Companies, Groups, Custom fields in Folk CRM 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 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
- 03 Sync folk people and companies with a marketing or outbound tool so outreach lists stay current.
- 04 Push enriched contact data from a data warehouse into folk custom fields.
Common sync patterns
Payment status on the account
Invoice and payment status from Recurly appears on the account in Folk CRM, so reps see overdue balances before they promise the next order.
Billing detail changes flow back
When a contact or address is corrected in Folk CRM, Recurly gets the update before the next invoice goes out.
Collections with context
Finance sees the account owner and relationship history from Folk CRM when chasing a balance, and sales sees that the chase is happening.
What you can sync between Folk CRM 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.
| Folk CRM objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Notes Free-text context attached to people and companies, readable for reporting. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Notes is specific to Folk CRM and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | 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. | Reminders is specific to Folk CRM and Accounts to Recurly — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | 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. | People is specific to Folk CRM and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Companies Organization records linked to people and kept aligned with billing or CS 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. | Companies is specific to Folk CRM and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Groups is specific to Folk CRM and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Custom fields is specific to Folk CRM and Transactions to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM 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.
Folk CRM Recurly Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Folk CRM 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Folk CRM: 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 Folk CRM ⇄ Recurly
Connect Folk CRM and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM 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 Folk CRM or Recurly record.
Observability
Monitoring
Track your Folk CRM ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Folk CRM and Recurly.
How the Folk CRM and Recurly connectors work
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a 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 Folk CRM 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 Folk CRM 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.
Folk CRM
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM 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 · Folk CRM ⇄ 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.
Folk CRM RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Recurly: authenticate both systems, choose the objects to sync (such as Folk CRM's Notes and Reminders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Folk CRM: REST API. Authentication: API key (Bearer token). 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.
-
Recurly: Records carry both opaque IDs and human-readable codes (account_code, plan_code); lookups can use either, which helps map to external keys. Folk CRM: Custom fields are defined per group, which means field mappings can differ across groups within the same workspace. Stacksync's field mapping accounts for these differences between Folk CRM and Recurly without custom code.
-
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 Folk CRM and Recurly records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Folk CRM and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Folk CRM–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Folk CRM and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 411 integrations available for Folk CRM and Recurly.
Popular · 6 of 411
-
Folk CRM ⇄ Chargebee -
Folk CRM ⇄ QuickBooks -
Recurly ⇄ Streak CRM -
Recurly ⇄ SugarCRM -
Recurly ⇄ Twenty CRM -
Recurly ⇄ Veeva CRM
No integrations match .
