Skip to content
Storage ⇄ CRM

Box to Chorusai integration — real-time, two-way sync

Keep Box and Chorusai 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 Box and Chorusai

Keep the paperwork with the relationship: Chorusai and Box share every customer's records and files in real time, in both directions.

Chorusai holds the customer relationship as structured records; Box holds the files that belong to those relationships, from contracts and proposals to signed agreements and statements of work. The two are linked in practice and disconnected in software: someone downloads a document, renames it, and uploads it to the right folder, or exports records out to storage for retention. Done by hand, files drift away from the records they belong to and copies fall out of date.

Stacksync keeps Recordings (Conversations), Users, Trackers, Deals in Chorusai aligned with Collaborations, Users, Groups, Tasks in Box, in real time. A new account or deal can open its own folder in Box; a document filed in Box can surface as a link and metadata on the matching record in Chorusai; and records from Chorusai can be written into Box as files or objects for backup, archival, and compliance. You choose which side owns what, and Stacksync keeps the two consistent as either one changes.

Common use cases

  • 01 Sync Trackers such as pricing, competitor, and next-steps mentions onto matching CRM Opportunities as coaching and deal-risk signals.
  • 02 Export Scorecards and their scores to a database to power rep-coaching and QA dashboards across sales teams.
  • 03 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
  • 04 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.

Common sync patterns

A folder per account or deal

When an account or deal is created in Chorusai, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.

Documents linked back to the record

A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Chorusai, so the customer's paperwork sits with the relationship instead of a shared drive.

CRM records archived into storage

Records from Chorusai are written into Box as files or objects on the schedule you set, giving you a durable copy for backup, retention, and compliance without an export to run by hand.

What you can sync between Box and Chorusai

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.

Box objects Chorusai objects How this pairing syncs
Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. Users Chorus users with roles and team membership; read to map engagement owners and participants to CRM and warehouse identities. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. Scorecards Call QA and coaching assessments with reviewer, recipient, and scores; read and exported for rep-performance reporting. Folders is specific to Box and Scorecards to Chorusai — each maps to any object or custom field on the other side.
Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. Moments Timestamped highlight clips from a conversation; created via the API to capture key call snippets. Metadata is specific to Box and Moments to Chorusai — each maps to any object or custom field on the other side.
Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. Playlists Curated collections of Moments and Recordings; created and managed to share coaching examples across teams. Collaborations is specific to Box and Playlists to Chorusai — each maps to any object or custom field on the other side.
Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. Engagements Meetings and dialer calls, the core record; filterable by date_time, participants, and processing_state, and polled incrementally to read conversation activity out. Groups is specific to Box and Engagements to Chorusai — each maps to any object or custom field on the other side.
Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. Recordings (Conversations) The recorded call with utterances, transcript, thumbnails, and metrics; read for analysis and uploaded or deleted through the API. Tasks is specific to Box and Recordings (Conversations) to Chorusai — each maps to any object or custom field on the other side.

How changes propagate between Box and Chorusai

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.

Box Chorusai Sub-second propagation

DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.

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

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

Rate-limit considerations

  • Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
  • Chorusai: Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes.
What ships with Box ⇄ Chorusai

Connect Box and Chorusai for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Box or Chorusai instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Box or Chorusai 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 Box or Chorusai record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Box and Chorusai.

How the Box and Chorusai connectors work

Box

Integration surface
REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
Authentication
OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
Change detection
V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.

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
Chorusai setup guide
How it works

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

    Choose tables

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

Box and Chorusai 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
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 518 integrations available for Box and Chorusai.

Popular · 6 of 518
All Box integrations All Chorusai 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