Skip to content
Business productivity ⇄ Accounting and finance

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

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

Connect the financial records in Recurly with the work happening in Monday, so both stay current without exports or copy-paste.

Recurly holds the financial truth: who the customers are, what they were billed, what they paid. Monday is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Plans, Invoices, Transactions, Line Items in Recurly and Groups, Updates, Users, Workspaces in Monday in sync, bi-directionally and in real time. Whatever records Monday keeps and whatever events it produces, the overlap with Recurly is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

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 Write closed deals or provisioning records from a CRM or ERP into monday.com Items to kick off delivery and onboarding boards.
  • 04 Mirror monday.com Boards, Groups, and Subitems into a warehouse for cross-project reporting on status and timelines without CSV exports.

Common sync patterns

Where Monday tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Where Monday handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Recurly next to the customer they are helping, without logging into the finance system.

Where Monday collects payments or triggers charges: events land in Recurly

Payment and charge activity flows into Recurly as it happens, so the books reflect reality without manual reconciliation.

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

Monday objects Recurly objects How this pairing syncs
Updates Comment and activity threads attached to items; read out into a database for reporting or written back as notes. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Updates is specific to Monday and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Users Account members referenced by people columns; read to resolve owner and assignee IDs to names and emails. 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). Users is specific to Monday and Billing Info to Recurly — each maps to any object or custom field on the other side.
Workspaces Top-level containers that hold boards; used to scope which boards a given sync covers. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Workspaces is specific to Monday and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.
Boards Table-like containers that hold items; each board maps to a synced table, and its columns define the field mapping. 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. Boards is specific to Monday and Accounts to Recurly — each maps to any object or custom field on the other side.
Items Rows within a board and the primary record; synced two-way and created, updated, archived, or deleted via GraphQL mutations. 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. Items is specific to Monday and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Subitems Nested rows under items, stored on a separate hidden board; synced as a child table linked to the parent item. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Subitems is specific to Monday and Plans to Recurly — each maps to any object or custom field on the other side.

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

Monday Recurly Sub-second propagation

DetectionMonday notifies Stacksync of record changes through webhook events. Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events.

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

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

Rate-limit considerations

  • Monday: Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window.
  • 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 Monday ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Monday and Recurly connectors work

Monday

Integration surface
GraphQL API (single endpoint, api.monday.com/v2)
Authentication
OAuth 2.0 for installed apps, or a per-user personal API token (admin/member scope); a date-based API version is sent via request header
Change detection
Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events; polling falls back to the item updated_at field
Capabilities
read · write · webhooks
Rate limits
Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window
Monday setup guide

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

    Choose tables

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

Monday 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 506 integrations available for Monday and Recurly.

Popular · 7 of 506
All Monday 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