Real-time
Two-way sync
Changes in Recurly or Rollworks instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Marketing
Recurly to Rollworks integration — real-time, two-way sync
Keep Recurly and Rollworks 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 Recurly and Rollworks
Put revenue reality behind every campaign: Recurly and Rollworks share the same customers, contacts, and billing status in real time, in both directions.
Recurly records the money — who pays, how much, and whether they are current; Rollworks decides who hears from the business and what they hear. The two overlap wherever the same customers and contacts matter to both, and when that overlap is bridged by CSV exports or an overnight batch, campaigns target on stale billing data and finance works from lists marketing has already changed underneath it.
Stacksync syncs Invoices, Transactions, Line Items, Coupons and Redemptions in Recurly with Reporting and Attribution, Target Account Lists, Account Tiers, Accounts (TAL Items) in Rollworks field by field, in real time, and in both directions. You decide which system owns which fields — finance keeps the revenue and payment truth, marketing keeps consent and engagement — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
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 Activate high-intent accounts by writing them into a Target Account List tier when a product or intent signal fires in an operational database.
- 04 Create and edit Prospecting v2 Campaigns and Ad Groups programmatically so budgets and targeting stay in step with an internal planning system.
Common sync patterns
One customer and contact list
Where both systems keep customer or contact records, an edit on either side propagates to the other, ending dual maintenance and the drift it creates.
Where Rollworks captures new people: clean records flow to finance
Registrants, form fills, or leads created in Rollworks create or update the matching customer or contact in Recurly, so billing and reporting start from accurate details without re-entry.
Where Recurly tracks lifecycle state: keep Rollworks current
Trial, renewal, churn, or payment state from Recurly updates the contact in Rollworks, so lifecycle campaigns and audience suppression run on current billing reality.
What you can sync between Recurly and Rollworks
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.
| Recurly objects | Rollworks objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. | Subscriptions is specific to Recurly and Reporting and Attribution to Rollworks — each maps to any object or custom field on the other side. | |
| Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. | Plans is specific to Recurly and Target Account Lists to Rollworks — each maps to any object or custom field on the other side. | |
| Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. | Invoices is specific to Recurly and Account Tiers to Rollworks — each maps to any object or custom field on the other side. | |
| Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. | Transactions is specific to Recurly and Accounts (TAL Items) to Rollworks — each maps to any object or custom field on the other side. | |
| Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. | Line Items is specific to Recurly and Audience Segments to Rollworks — each maps to any object or custom field on the other side. | |
| Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. | Coupons and Redemptions is specific to Recurly and Campaigns to Rollworks — each maps to any object or custom field on the other side. |
How changes propagate between Recurly and Rollworks
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.
Recurly Rollworks 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 Rollworks through its API, with automatic retries and rate-limit backoff.
Rollworks Recurly Interval-based propagation
DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- 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.
- Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
What ships with Recurly ⇄ Rollworks
Connect Recurly and Rollworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Recurly–Rollworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Recurly or Rollworks 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 Recurly or Rollworks record.
Observability
Monitoring
Track your Recurly ⇄ Rollworks sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Recurly and Rollworks.
How the Recurly and Rollworks connectors work
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.
Rollworks
- Integration surface
- REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
- Authentication
- OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
- Change detection
- Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
- Capabilities
- read · write
- Rate limits
- NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
How it works
How to connect Recurly to Rollworks — 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.
- 01
Connect your apps
Authenticate Recurly and Rollworks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Recurly
connected
Rollworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Recurly and Rollworks 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.
objects · Recurly ⇄ RollworksCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Recurly RollworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Recurly and Rollworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Recurly and Rollworks: authenticate both systems, choose the objects to sync (such as Recurly's Subscriptions and Plans), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Recurly and Rollworks connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Recurly–Rollworks integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Recurly and Rollworks. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Recurly: 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. On Rollworks: Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Invoices, Transactions, Line Items, Coupons and Redemptions, plus custom fields where Recurly exposes them. On the Rollworks side: Reporting and Attribution, Target Account Lists, Account Tiers, Accounts (TAL Items). Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 365 integrations available for Recurly and Rollworks.
Popular · 7 of 365
-
Recurly ⇄ Twitter Ads -
Recurly ⇄ Marketo -
Recurly ⇄ Salesforce Marketing Cloud -
Recurly ⇄ Cvent -
Rollworks ⇄ Workday -
Rollworks ⇄ Anaplan -
Rollworks ⇄ Chargebee
No integrations match .
