Skip to content
Human resources ⇄ Accounting and finance

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

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

Keep the employee, department, and cost records that Recurly and Namely share consistent in real time, so the finance system and the people system stop drifting apart.

Recurly runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Namely runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Measured Units and Usage, Accounts, Subscriptions, Plans in Recurly with Events, Profiles, Job Titles, Job Tiers in Namely bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

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 Feed Namely Reports as JSON into a database on a schedule for roster, turnover, and diversity dashboards without manual CSV exports.
  • 04 Provision or deprovision accounts in an IdP or directory when a Profile's user_status or start_date changes, and write the resulting user ID and email back onto the Profile.

Common sync patterns

One employee identity

A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.

Department and cost-center alignment

The org structure maintained in Namely keeps the departments or cost centers in Recurly current, so spend and headcount roll up the same way.

Status changes propagate

A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.

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

Namely objects Recurly objects How this pairing syncs
Groups Departments and locations that organize Profiles; synced to keep org structure aligned with a warehouse or IdP. 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. Groups is specific to Namely and Accounts to Recurly — each maps to any object or custom field on the other side.
Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. 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. Teams is specific to Namely and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Reports Saved Namely reports returned as JSON snapshots that update instantly; read-only feeds for headcount and roster analytics. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Reports is specific to Namely and Plans to Recurly — each maps to any object or custom field on the other side.
Profile Fields Metadata describing standard and company-defined custom field sections; read to discover schema and generate mappings. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Profile Fields is specific to Namely and Invoices to Recurly — each maps to any object or custom field on the other side.
Events Home-feed items such as announcements, birthdays, anniversaries, and new arrivals; typically read-only into comms tools. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Events is specific to Namely and Transactions to Recurly — each maps to any object or custom field on the other side.
Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Profiles is specific to Namely and Line Items to Recurly — each maps to any object or custom field on the other side.

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

Namely Recurly Interval-based propagation

DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.

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

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

Rate-limit considerations

  • Namely: Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
  • 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 Namely ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Namely and Recurly connectors work

Namely

Integration surface
REST API (JSON over HTTPS)
Authentication
OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1
Change detection
No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes
Capabilities
read · write
Rate limits
Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.

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

    Choose tables

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

Namely 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
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 398 integrations available for Namely and Recurly.

Popular · 7 of 398
All Namely 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