Real-time
Two-way sync
Changes in Folk CRM or Zuora instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Folk CRM to Zuora integration — real-time, two-way sync
Keep Folk CRM and Zuora 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 Zuora
Sync customers, invoices, and payment status between Zuora 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. Zuora 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 Usage, Order and Amendment, Account (Billing Account), Subscription in Zuora to Companies, Groups, Custom fields, Notes 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 Master the Product Catalog (Products and Product Rate Plans) in a database or PIM and write pricing changes into Zuora.
- 02 Stream metered Usage records from a warehouse or metering pipeline into Zuora so consumption-based charges are rated on the correct Rate Plan.
- 03 Keep folk and a billing or customer success tool aligned on company records as deals close.
- 04 Sync folk people and companies with a marketing or outbound tool so outreach lists stay current.
Common sync patterns
Payment status on the account
Invoice and payment status from Zuora 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, Zuora 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 Zuora
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 | Zuora objects | How this pairing syncs | |
|---|---|---|---|
| Notes Free-text context attached to people and companies, readable for reporting. | Account (Billing Account) The customer billing entity holding contacts, payment methods, and billing settings; synced two-way as the parent record most other Zuora objects hang off. | Notes is specific to Folk CRM and Account (Billing Account) to Zuora — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | Subscription Recurring or usage-based subscription tied to an Account; read for revenue state and written when provisioning or changing plans from a CRM or app. | Reminders is specific to Folk CRM and Subscription to Zuora — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | Rate Plan and Rate Plan Charge The priced components inside a Subscription; synced so charge amounts, quantities, and effective dates stay aligned with the source system. | People is specific to Folk CRM and Rate Plan and Rate Plan Charge to Zuora — 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. | Product and Product Rate Plan (Product Catalog) The catalog of sellable products and their pricing; usually mastered elsewhere and written into Zuora, or read to map subscription charges. | Companies is specific to Folk CRM and Product and Product Rate Plan (Product Catalog) to Zuora — 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. | Invoice Billing documents generated from rate plan charges and order line items; typically read out into an ERP or GL for revenue recognition and reconciliation. | Groups is specific to Folk CRM and Invoice to Zuora — 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. | Payment Payment and refund transactions applied against invoices; read for cash application, dunning, and reconciliation reporting in the warehouse. | Custom fields is specific to Folk CRM and Payment to Zuora — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM and Zuora
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 Zuora 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 Zuora through its API, with automatic retries and rate-limit backoff.
Zuora Folk CRM Sub-second propagation
DetectionZuora notifies Stacksync of record changes through webhook events. Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for.
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.
- Zuora: Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
What ships with Folk CRM ⇄ Zuora
Connect Folk CRM and Zuora for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Zuora connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM or Zuora 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 Zuora record.
Observability
Monitoring
Track your Folk CRM ⇄ Zuora 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 Zuora.
How the Folk CRM and Zuora 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
Zuora
- Integration surface
- REST API (v1) with Object Query, Data Query, and AQuA bulk export; legacy SOAP API also available
- Authentication
- OAuth 2.0 client credentials (bearer token, 3600s expiry); access is governed by the Zuora role of the OAuth client's associated user, with no granular scopes
- Change detection
- Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes
- Capabilities
- read · write · webhooks
- Rate limits
- Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
How it works
How to connect Folk CRM to Zuora — 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 Zuora 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
Zuora
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM and Zuora 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 ⇄ ZuoraCustomers 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 ZuoraCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Zuora integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Zuora: 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.
-
Yes — Stacksync ships production-grade connectors for both Folk CRM and Zuora. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. On Zuora: Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Zuora side: Usage, Order and Amendment, Account (Billing Account), Subscription, plus custom fields where Zuora exposes them. On the Folk CRM side: Companies, Groups, Custom fields, Notes. 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 Folk CRM and Zuora: Payment status on the account; Billing detail changes flow back; Collections with context. Invoice and payment status from Zuora appears on the account in Folk CRM, so reps see overdue balances before they promise the next order.
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 Zuora.
Popular · 6 of 411
No integrations match .
