Skip to content
CRM ⇄ Accounting and finance

Close to Zuora integration — real-time, two-way sync

Keep Close 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 Close and Zuora

Sync customers, invoices, and payment status between Zuora and Close in real time, so sales sees the money and finance sees the relationship.

Finance and sales describe the same customers in different systems. Close 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 Subscription, Rate Plan and Rate Plan Charge, Product and Product Rate Plan (Product Catalog), Invoice in Zuora to Custom Activities, Custom Fields, Users, Smart Views in Close 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 Stream metered Usage records from a warehouse or metering pipeline into Zuora so consumption-based charges are rated on the correct Rate Plan.
  • 02 Two-way sync of Accounts and Subscriptions with an operational Postgres database so product and finance teams read billing state in SQL while changes flow back into Zuora.
  • 03 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • 04 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.

Common sync patterns

Collections with context

Finance sees the account owner and relationship history from Close when chasing a balance, and sales sees that the chase is happening.

Where Close tracks deals: closed-won creates the finance record

A won opportunity creates or updates the customer in Zuora with the right billing details, so invoicing starts without re-keying.

Payment status on the account

Invoice and payment status from Zuora appears on the account in Close, so reps see overdue balances before they promise the next order.

What you can sync between Close 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.

Close objects Zuora objects How this pairing syncs
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Usage Metered consumption records; written into Zuora from a metering or warehouse pipeline so consumption-based charges are rated and invoiced. Custom Activities is specific to Close and Usage to Zuora — each maps to any object or custom field on the other side.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Order and Amendment Records of subscription create and change actions; written to Zuora to drive quote-to-cash and read for subscription change history. Custom Fields is specific to Close and Order and Amendment to Zuora — each maps to any object or custom field on the other side.
Users Sales reps referenced as owners on leads, opportunities, and activities. 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. Users is specific to Close and Account (Billing Account) to Zuora — each maps to any object or custom field on the other side.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. 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. Smart Views is specific to Close and Subscription to Zuora — each maps to any object or custom field on the other side.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. 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. Leads is specific to Close and Rate Plan and Rate Plan Charge to Zuora — each maps to any object or custom field on the other side.
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. 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. Contacts is specific to Close and Product and Product Rate Plan (Product Catalog) to Zuora — each maps to any object or custom field on the other side.

How changes propagate between Close 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.

Close Zuora Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

DeliveryEach detected change is written to Zuora through its API, with automatic retries and rate-limit backoff.

Zuora Close 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 Close through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • 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 Close ⇄ Zuora

Connect Close and Zuora for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Zuora connection.

Real-time

Two-way sync

Changes in Close or Zuora instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Close 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 Close or Zuora record.

Observability

Monitoring

Track your Close ⇄ Zuora sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and Zuora.

How the Close and Zuora connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

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 Close 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.

  1. 01

    Connect your apps

    Authenticate Close 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Close connected
    Zuora connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Close 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Close ⇄ Zuora
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Close Zuora
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Close and Zuora integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 524 integrations available for Close and Zuora.

Popular · 8 of 524
All Close integrations All Zuora integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own