Skip to content
Business productivity ⇄ Accounting and finance

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

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

Connect the financial records in Recurly with the work happening in Agiloft, 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. Agiloft 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 Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts in Recurly and Custom tables, Contracts, Companies, People in Agiloft in sync, bi-directionally and in real time. Whatever records Agiloft 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 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 03 Write contract or company records into Agiloft when a deal closes in the CRM to kick off downstream legal and procurement workflows.
  • 04 Two-way sync Contracts between Agiloft and an ERP or warehouse so value, renewal dates, and status stay current without manual re-keying.

Common sync patterns

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

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

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

Agiloft objects Recurly objects How this pairing syncs
Companies Records for every organization - counterparties, vendors, customers - linked to contracts and people; read and written to keep account master data aligned with a CRM or ERP. 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). Companies is specific to Agiloft and Billing Info to Recurly — each maps to any object or custom field on the other side.
People Parent table for individuals, split into Employees (internal users) and Contacts (external company contacts); synced to map signers, approvers, and account owners to CRM or HR records. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. People is specific to Agiloft and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.
Attachments File records holding the executed contract PDFs and supporting documents linked to a contract; read to pull signed files out, or written to push generated documents in. 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. Attachments is specific to Agiloft and Accounts to Recurly — each maps to any object or custom field on the other side.
Approvals Per-record approval instances generated from Approval Templates and Workflows; read to report approval status and cycle time, or written to trigger and record decisions. 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. Approvals is specific to Agiloft and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Tasks Assigned action items with owners, due dates, and states tied to contracts or projects; synced two-way to surface Agiloft work inside a PM or operations system. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Tasks is specific to Agiloft and Plans to Recurly — each maps to any object or custom field on the other side.
Clause Library Reusable, approved contract clauses with metadata and categories; read to feed clause content into other systems or reporting, or maintained from an external source of truth. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Clause Library is specific to Agiloft and Invoices to Recurly — each maps to any object or custom field on the other side.

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

Agiloft Recurly Sub-second propagation

DetectionAgiloft notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL.

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

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

Rate-limit considerations

  • Agiloft: Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
  • 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 Agiloft ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Agiloft and Recurly connectors work

Agiloft

Integration surface
REST API (/ewws/rest/{kb}) and SOAP/EWS v2 web services (EWWSv2Service WSDL), plus a native Webhooks subscription API
Authentication
OAuth 2.0 via OAuth2 Client Setup - Authorization Code with PKCE for user-delegated apps and Client Credentials for machine-to-machine; also JWT tokens or Basic Auth with a session token from POST /ewws/rest/{kb}/login
Change detection
Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log.
Capabilities
read · write · webhooks
Rate limits
Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.

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

    Choose tables

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

Agiloft 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 402 integrations available for Agiloft and Recurly.

Popular · 7 of 402
All Agiloft 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