Real-time
Two-way sync
Changes in Box or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Twenty CRM integration — real-time, two-way sync
Keep Box and Twenty CRM 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 Twenty CRM
Keep the paperwork with the relationship: Twenty CRM and Box share every customer's records and files in real time, in both directions.
Twenty CRM 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 Custom Objects, Attachments, Workspace Members, People in Twenty CRM aligned with Metadata, Collaborations, Users, Groups 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 Twenty CRM; and records from Twenty CRM 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 Mirror support tickets or tasks between Twenty and an operations tool.
- 02 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- 03 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
- 04 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.
Common sync patterns
CRM records archived into storage
Records from Twenty CRM 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.
Document status on the record
Metadata kept in Box, such as document type, review state, or whether an agreement is signed, updates a field on the matching record in Twenty CRM, so people working the account see where the paperwork stands without opening storage.
One place for a customer's files
Attachments that accumulate against a record in Twenty CRM collect in that customer's folder in Box, so the full document history lives in one place and is reachable by anyone who needs it.
What you can sync between Box and Twenty CRM
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 | Twenty CRM objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Tasks To-dos linked to people, companies, or deals. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Attachments Files linked to records. | Collaborations is specific to Box and Attachments to Twenty CRM — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Workspace Members User accounts used for record ownership and assignment mapping. | Users is specific to Box and Workspace Members to Twenty CRM — 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. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Groups is specific to Box and People to Twenty CRM — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Companies Account-level records that group people and opportunities. | Events is specific to Box and Companies to Twenty CRM — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Opportunities Deal records tracked through pipeline stages, synced for forecasting. | Files is specific to Box and Opportunities to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Box and Twenty CRM
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 Twenty CRM 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 Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Box Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
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.
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Box ⇄ Twenty CRM
Connect Box and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Twenty CRM 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 Twenty CRM record.
Observability
Monitoring
Track your Box ⇄ Twenty CRM 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 Twenty CRM.
How the Box and Twenty CRM 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.
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Box to Twenty CRM — 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 Box and Twenty CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Box
connected
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Twenty CRM 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 · Box ⇄ Twenty CRMCustomers 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.
Box Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Twenty CRM: authenticate both systems, choose the objects to sync (such as Box's Tasks and Collaborations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Twenty CRM side: Custom Objects, Attachments, Workspace Members, People, plus custom fields where Twenty CRM exposes them. On the Box side: Metadata, Collaborations, Users, Groups. 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 Box and Twenty CRM: CRM records archived into storage; Document status on the record; One place for a customer's files. Records from Twenty CRM 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.
-
Box: 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. Twenty CRM: GraphQL and REST APIs. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
-
Twenty CRM: Both GraphQL and REST APIs are generated from the workspace's object schema, so custom objects get the same API surface as standard ones. Box: Rate limits are enforced per user; hitting them returns HTTP 429, and clients are expected to honor the Retry-After header with exponential backoff. Stacksync's field mapping accounts for these differences between Box and Twenty CRM without custom code.
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
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 426 integrations available for Box and Twenty CRM.
Popular · 7 of 426
-
Box ⇄ Veeva CRM -
Box ⇄ Vtiger CRM -
Box ⇄ Zoho SalesIQ -
Box ⇄ ZoomInfo -
Twenty CRM ⇄ Egnyte -
Twenty CRM ⇄ Amazon S3 -
Twenty CRM ⇄ Sharepoint
No integrations match .
