Skip to content
CRM ⇄ Accounting and finance

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

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

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

Finance and sales describe the same customers in different systems. Clari 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 Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts in Recurly to Account field extensions, Opportunity field extensions, Audit Events, Forecast in Clari 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 Pull Activity (Capture) meetings and emails, mapped to their accounts and opportunities, into a database for coverage and engagement analysis.
  • 04 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.

Common sync patterns

Where Clari 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 Clari, so reps see overdue balances before they promise the next order.

Billing detail changes flow back

When a contact or address is corrected in Clari, Recurly gets the update before the next invoice goes out.

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

Clari objects Recurly objects How this pairing syncs
Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Quota is specific to Clari and Invoices to Recurly — each maps to any object or custom field on the other side.
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. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Opportunities is specific to Clari and Transactions to Recurly — each maps to any object or custom field on the other side.
Activity (Capture) Meetings, emails, and attachments captured by Clari and mapped to accounts and opportunities; exported read-only via async activity jobs. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Activity (Capture) is specific to Clari and Line Items to Recurly — each maps to any object or custom field on the other side.
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. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Account field extensions is specific to Clari and Coupons and Redemptions to Recurly — 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. 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). Opportunity field extensions is specific to Clari and Billing Info to Recurly — 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. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Audit Events is specific to Clari and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.

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

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

Recurly Clari 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 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.
  • 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 Clari ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Clari ⇄ Recurly 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 Recurly.

How the Clari and Recurly 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.

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

  1. 01

    Connect your apps

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

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Clari connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Clari ⇄ Recurly
    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 Recurly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Clari and Recurly 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 417 integrations available for Clari and Recurly.

Popular · 5 of 417
All Clari integrations All Recurly 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