Real-time
Two-way sync
Changes in Chorusai or Reltio instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Database
Chorusai to Reltio integration — real-time, two-way sync
Keep Chorusai and Reltio 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 Chorusai and Reltio
Treat Chorusai like part of your database: its records live in Reltio as real tables, and writes in either place sync to the other in seconds.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Reltio, where it can be queried and joined like everything else.
Stacksync mirrors Playlists, Engagements, Recordings (Conversations), Users from Chorusai into Interactions, Matches (Potential Matches), Activity Log, Data Change Requests (DCR) in Reltio with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Chorusai with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Common use cases
- 01 Upload externally recorded dialer or web-conference audio into Chorus as Recordings so it gets transcribed and analyzed like native calls.
- 02 Sync Trackers such as pricing, competitor, and next-steps mentions onto matching CRM Opportunities as coaching and deal-risk signals.
- 03 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
- 04 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
Common sync patterns
Product events onto CRM records
Signup, usage, or lifecycle changes written to Reltio sync onto the matching records in Chorusai, giving go-to-market teams live product context.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Chorusai API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Chorusai arrive as row changes in Reltio, ready to drive jobs and notifications.
What you can sync between Chorusai and Reltio
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.
| Chorusai objects | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Users Chorus users with roles and team membership; read to map engagement owners and participants to CRM and warehouse identities. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Users is specific to Chorusai and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Trackers AI keyword and topic trackers (pricing, competitors, next steps) surfaced within a conversation; read out as coaching and deal-risk signals. | Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Trackers is specific to Chorusai and Crosswalks to Reltio — each maps to any object or custom field on the other side. | |
| Deals CRM opportunity context attached to a conversation (account, deal, owner); read to attribute call activity to open pipeline. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Deals is specific to Chorusai and Interactions to Reltio — each maps to any object or custom field on the other side. | |
| Scorecards Call QA and coaching assessments with reviewer, recipient, and scores; read and exported for rep-performance reporting. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Scorecards is specific to Chorusai and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. | |
| Moments Timestamped highlight clips from a conversation; created via the API to capture key call snippets. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Moments is specific to Chorusai and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Playlists Curated collections of Moments and Recordings; created and managed to share coaching examples across teams. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Playlists is specific to Chorusai and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Chorusai and Reltio
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.
Chorusai Reltio Interval-based propagation
DetectionStacksync polls Chorusai for changes on an incremental schedule, reading only records changed since the previous pass. Polling the engagements endpoint on date_time and processing_state.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Chorusai Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to Chorusai through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Chorusai: Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes.
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Chorusai ⇄ Reltio
Connect Chorusai and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Chorusai–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Chorusai or Reltio 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 Chorusai or Reltio record.
Observability
Monitoring
Track your Chorusai ⇄ Reltio sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Chorusai and Reltio.
How the Chorusai and Reltio connectors work
Chorusai
- Integration surface
- REST API (api-docs.chorus.ai)
- Authentication
- Per-user API token generated in Chorus Personal Settings, sent in the Authorization request header
- Change detection
- Polling the engagements endpoint on date_time and processing_state; no public change webhooks or CDC
- Capabilities
- read · write
- Rate limits
- Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect Chorusai to Reltio — 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 Chorusai and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Chorusai
connected
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Chorusai and Reltio 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 · Chorusai ⇄ ReltioCustomers 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.
Chorusai ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Chorusai and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Chorusai and Reltio: authenticate both systems, choose the objects to sync (such as Chorusai's Users and Trackers), 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 Chorusai and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Chorusai–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Chorusai and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Chorusai: Polling the engagements endpoint on date_time and processing_state; no public change webhooks or CDC. On Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Chorusai side: Playlists, Engagements, Recordings (Conversations), Users, plus custom fields where Chorusai exposes them. On the Reltio side: Interactions, Matches (Potential Matches), Activity Log, Data Change Requests (DCR). 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
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 452 integrations available for Chorusai and Reltio.
Popular · 8 of 452
-
Chorusai ⇄ MySQL -
Chorusai ⇄ MariaDB -
Chorusai ⇄ SQL Server -
Chorusai ⇄ Postgres Heroku -
Reltio ⇄ Attio -
Reltio ⇄ Pipedrive -
Reltio ⇄ Zoho CRM -
Reltio ⇄ Shopify
No integrations match .
