Two-way sync
Changes in Chorusai or Pigment instantly reflect in both systems. No stale data, no manual imports.
Keep Chorusai and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Finance and sales describe the same customers in different systems. Chorusai knows the relationship: who the contacts are and what is in motion with the account. Pigment knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Scenarios, Data imports, Users and permissions, Applications in Pigment to Deals, Scorecards, Moments, Playlists in Chorusai with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
When a contact or address is corrected in Chorusai, Pigment gets the update before the next invoice goes out.
Finance sees the account owner and relationship history from Chorusai when chasing a balance, and sales sees that the chase is happening.
A won opportunity creates or updates the customer in Pigment with the right billing details, so invoicing starts without re-keying.
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 | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Trackers AI keyword and topic trackers (pricing, competitors, next steps) surfaced within a conversation; read out as coaching and deal-risk signals. | Tables Row-based transactional data loaded into models from source systems | Trackers is specific to Chorusai and Tables to Pigment — 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. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Deals is specific to Chorusai and Scenarios to Pigment — 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. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Scorecards is specific to Chorusai and Data imports to Pigment — 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. | Users and permissions Access controls governing which model areas a sync can touch | Moments is specific to Chorusai and Users and permissions to Pigment — 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. | Applications Planning models organized by domain such as finance, sales, or workforce | Playlists is specific to Chorusai and Applications to Pigment — each maps to any object or custom field on the other side. | |
| Engagements Meetings and dialer calls, the core record; filterable by date_time, participants, and processing_state, and polled incrementally to read conversation activity out. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Engagements is specific to Chorusai and Metrics to Pigment — each maps to any object or custom field on the other side. |
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.
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 Pigment through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is written to Chorusai through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Chorusai–Pigment connection.
Changes in Chorusai or Pigment instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Chorusai or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Chorusai or Pigment record.
Track your Chorusai ⇄ Pigment sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Chorusai and Pigment.
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.
Authenticate Chorusai and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Chorusai and Pigment 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Chorusai and Pigment: authenticate both systems, choose the objects to sync (such as Chorusai's Trackers and Deals), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Chorusai: Polling the engagements endpoint on date_time and processing_state; no public change webhooks or CDC. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Pigment side: Scenarios, Data imports, Users and permissions, Applications, plus custom fields where Pigment exposes them. On the Chorusai side: Deals, Scorecards, Moments, Playlists. 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.
Common patterns for Chorusai and Pigment: Billing detail changes flow back; Collections with context; Where Chorusai tracks deals: closed-won creates the finance record. When a contact or address is corrected in Chorusai, Pigment gets the update before the next invoice goes out.
Chorusai: REST API (api-docs.chorus.ai). Authentication: Per-user API token generated in Chorus Personal Settings, sent in the Authorization request header. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 432 integrations available for Chorusai and Pigment.