Skip to content
CRM

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

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

Run Clari and Close side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.

Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.

Stacksync syncs Opportunities, Activity (Capture), Account field extensions, Opportunity field extensions in Clari with Opportunities, Activities, Tasks, Custom Activities in Close in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.

Common use cases

  • 01 Write warehouse-computed health scores and usage metrics onto Clari Opportunity records as field extensions via the ingest API so deal reviews show product signals.
  • 02 Enrich Clari Account records with firmographic or billing data points through the ingest API in incremental mode.
  • 03 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • 04 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.

Common sync patterns

Where both track pipeline: deal visibility across systems

Deal stage and value on shared accounts stay visible from either CRM.

Post-acquisition consolidation

Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.

Migration with a parallel run

When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.

What you can sync between Clari and Close

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.

Clari objects Close objects How this pairing syncs
Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Account field extensions External data points written onto Account records through the ingest API in initial or incremental mode; requires an apikey plus a partnerkey. Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Account field extensions is specific to Clari and Custom Fields to Close — each maps to any object or custom field on the other side.
Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. Users Sales reps referenced as owners on leads, opportunities, and activities. Opportunity field extensions is specific to Clari and Users to Close — each maps to any object or custom field on the other side.
Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Audit Events is specific to Clari and Smart Views to Close — each maps to any object or custom field on the other side.
Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. Forecast is specific to Clari and Leads to Close — each maps to any object or custom field on the other side.
Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Quota is specific to Clari and Contacts to Close — each maps to any object or custom field on the other side.

How changes propagate between Clari and Close

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.

Clari Close Interval-based propagation

DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).

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

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

Rate-limit considerations

  • Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
  • Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Clari ⇄ Close

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Clari and Close connectors work

Clari

Integration surface
REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
Authentication
API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
Change detection
Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
Capabilities
read · write
Rate limits
Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.

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
How it works

How to connect Clari to Close — 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 Clari and Close 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
    Clari connected
    Close connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Clari and Close 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 · Clari ⇄ Close
    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
    Clari Close
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Clari and Close 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 445 integrations available for Clari and Close.

Popular · 8 of 445
All Clari integrations All Close 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