Skip to content
Business productivity ⇄ Accounting and finance

Customer.io to Rillet integration — real-time, two-way sync

Keep Customer.io and Rillet 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 Customer.io and Rillet

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

Rillet holds the financial truth: who the customers are, what they were billed, what they paid. Customer.io 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 Reimbursement, Custom Field, Account, Customer in Rillet and Events, Segments, Campaigns, Broadcasts in Customer.io in sync, bi-directionally and in real time. Whatever records Customer.io keeps and whatever events it produces, the overlap with Rillet 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

  • Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • Sync AR and collection status back to customer success tools ahead of renewals.
  • Push CRM segments and lead status into Customer.io so messaging respects sales stage.
  • Land delivery and engagement events (sent, opened, clicked, bounced) from reporting webhooks into a warehouse for attribution analysis.

Where Customer.io collects payments or triggers charges: events land in Rillet

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

Where Customer.io 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 Customer.io is a docs or knowledge workspace: reference data kept fresh

Figures teams rely on, like customer status or outstanding balances, stay current wherever Customer.io surfaces them instead of going stale after a one-time paste.

What you can sync between Customer.io and Rillet

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.

Customer.io objects Rillet objects
Events Behavioral events sent via the Track API that trigger campaigns. Journal Entry Synced with incremental and full sync per the Stacksync docs.
Segments Attribute- or event-based groups; data syncs feed the attributes segments evaluate. Invoice Payment Synced with incremental and full sync per the Stacksync docs.
Campaigns Automated workflows whose membership and metrics can be read via the App API. Charge Synced with incremental and full sync per the Stacksync docs.
Broadcasts One-off sends to segments or audiences, triggerable via API. Reimbursement Synced with incremental and full sync per the Stacksync docs.
Deliveries / Messages Per-recipient message records whose lifecycle events flow out through reporting webhooks. Custom Field Synced with incremental and full sync per the Stacksync docs.
Newsletters Recurring email sends with performance metrics available for reporting syncs. Account Synced with incremental and full sync per the Stacksync docs.
What ships with Customer.io ⇄ Rillet

Connect Customer.io and Rillet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Customer.io–Rillet connection.

Real-time

Two-way sync

Changes in Customer.io or Rillet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Customer.io or Rillet 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 Customer.io or Rillet record.

Observability

Monitoring

Track your Customer.io ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Customer.io and Rillet.

How the Customer.io and Rillet connectors work

Customer.io

Integration surface
REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
Authentication
Basic auth with site ID and API key for the Track API; bearer token for the App API
Change detection
Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
Capabilities
read · write · webhooks
Rate limits
Subject to per-API rate limits documented by Customer.io

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

How to connect Customer.io to Rillet — 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 Customer.io and Rillet 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
    Customer.io connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Customer.io and Rillet 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 · Customer.io ⇄ Rillet
    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
    Customer.io Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Customer.io and Rillet integration FAQ

SECURITY

Security teams love 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 386 integrations available for Customer.io and Rillet.

Popular · 8 of 386
All Customer.io integrations All Rillet 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