Skip to content
CRM ⇄ Accounting and finance

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

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

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

Finance and sales describe the same customers in different systems. Freshsales 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 Line Items, Coupons and Redemptions, Billing Info, Measured Units and Usage in Recurly to Notes, Sales activities, Products, Contacts in Freshsales 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 Push product-qualified leads from the warehouse into Freshsales as contacts with lifecycle stages set.
  • 04 Keep Freshsales accounts aligned with a billing system so plan and revenue fields stay current.

Common sync patterns

Billing detail changes flow back

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

Collections with context

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

Where Freshsales 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.

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

Freshsales objects Recurly objects How this pairing syncs
Accounts Company records kept aligned with billing, ERP, and warehouse tables. 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. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Tasks Rep to-dos created from external triggers or synced for productivity reporting. 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). Tasks is specific to Freshsales and Billing Info to Recurly — each maps to any object or custom field on the other side.
Appointments Scheduled meetings readable for activity analytics. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Appointments is specific to Freshsales and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.
Notes Free-text records attached to contacts, accounts, and deals. 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. Notes is specific to Freshsales and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Sales activities Configurable activity types logged against records, useful for engagement scoring. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Sales activities is specific to Freshsales and Plans to Recurly — each maps to any object or custom field on the other side.
Products Catalog items attached to deals for line-level revenue data. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Products is specific to Freshsales and Invoices to Recurly — each maps to any object or custom field on the other side.

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

Freshsales Recurly Sub-second propagation

DetectionFreshsales notifies Stacksync of record changes through webhook events. Polling with updated-at filters through views.

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

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

Rate-limit considerations

  • Freshsales: Subject to per-account API rate limits that vary by Freshworks plan.
  • 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 Freshsales ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Freshsales and Recurly.

How the Freshsales and Recurly connectors work

Freshsales

Integration surface
REST API
Authentication
API key sent as a Token authorization header
Change detection
Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that vary by Freshworks plan

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 Freshsales 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 Freshsales 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
    Freshsales connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Freshsales 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 517 integrations available for Freshsales and Recurly.

Popular · 8 of 517
All Freshsales 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