Real-time
Real-time sync
Changes in Box or ZoomInfo instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to ZoomInfo integration — real-time data sync
Keep Box and ZoomInfo 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 ZoomInfo
Flow ZoomInfo data into Box in real time — no exports, no schedulers, no custom scripts.
ZoomInfo is a read-only source: Stacksync reads its data in real time and delivers it into Box, so Box always reflects the current state of ZoomInfo — without exports, scripts, or schedulers.
ZoomInfo 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 Technographics, Company Hierarchies, Company Profiles, Contact Profiles in ZoomInfo aligned with Groups, Tasks, Events, Files 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 ZoomInfo; and records from ZoomInfo 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 Enrich CRM accounts and contacts on a schedule so firmographics, titles, and phone numbers stay current.
- 02 Sync intent signals into the CRM or warehouse to trigger outbound plays on in-market accounts.
- 03 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.
- 04 Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.
Common sync patterns
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 ZoomInfo, 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 ZoomInfo 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.
A folder per account or deal
When an account or deal is created in ZoomInfo, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.
What you can sync between Box and ZoomInfo
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 | ZoomInfo objects | How this pairing syncs | |
|---|---|---|---|
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Intent Signals Company-level topic scores indicating in-market buying behavior. | Groups is specific to Box and Intent Signals to ZoomInfo — 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. | Scoops Event-driven signals such as leadership changes, funding rounds, and new projects. | Tasks is specific to Box and Scoops to ZoomInfo — 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. | Technographics Technology install data per company, used for segmentation and territory planning. | Events is specific to Box and Technographics to ZoomInfo — 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. | Company Hierarchies Parent and subsidiary linkage used to align CRM account hierarchies. | Files is specific to Box and Company Hierarchies to ZoomInfo — each maps to any object or custom field on the other side. | |
| 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. | Company Profiles Firmographic records covering industry, size, revenue, and location, matched against CRM accounts. | Folders is specific to Box and Company Profiles to ZoomInfo — 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. | Contact Profiles Person records with title, email, phone, and company linkage, used to enrich leads and contacts. | Metadata is specific to Box and Contact Profiles to ZoomInfo — each maps to any object or custom field on the other side. |
How changes propagate between Box and ZoomInfo
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 ZoomInfo 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.
DeliveryZoomInfo does not accept inbound record writes, so this direction carries requests rather than records: ZoomInfo's output flows back as field updates on the originating Box records.
ZoomInfo Box Interval-based propagation
DetectionStacksync polls ZoomInfo for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled re-enrichment and polling.
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.
- ZoomInfo: Usage is metered by credits and contract-based limits rather than a single public rate limit.
What ships with Box ⇄ ZoomInfo
Connect Box and ZoomInfo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–ZoomInfo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or ZoomInfo 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 ZoomInfo record.
Observability
Monitoring
Track your Box ⇄ ZoomInfo 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 ZoomInfo.
How the Box and ZoomInfo 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.
ZoomInfo
- Integration surface
- REST API organized around search and enrich endpoints
- Authentication
- API credentials exchanged for a short-lived JWT
- Change detection
- Scheduled re-enrichment and polling; the platform is primarily a lookup and enrichment source, not an event stream
- Capabilities
- read
- Rate limits
- Usage is metered by credits and contract-based limits rather than a single public rate limit.
How it works
How to connect Box to ZoomInfo — 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 ZoomInfo 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
ZoomInfo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and ZoomInfo 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 ⇄ ZoomInfoCustomers 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 ZoomInfoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and ZoomInfo integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Box and ZoomInfo — ZoomInfo is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
ZoomInfo is a read-only source, so this integration runs one-way: Stacksync reads from ZoomInfo in real time and delivers into Box. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Box and ZoomInfo: Document status on the record; One place for a customer's files; A folder per account or deal. Metadata kept in Box, such as document type, review state, or whether an agreement is signed, updates a field on the matching record in ZoomInfo, so people working the account see where the paperwork stands without opening storage.
-
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. ZoomInfo: REST API organized around search and enrich endpoints. Authentication: API credentials exchanged for a short-lived JWT. Stacksync manages authentication, retries, and rate limits on both sides.
-
ZoomInfo: Intent data is delivered as company-level topic scores rather than person-level events, which shapes how it maps onto CRM records. Box: Server-auth apps (JWT or CCG) act through a service account and only see content that account owns or is collaborated on, unless enterprise as-user or admin scopes are granted. Stacksync's field mapping accounts for these differences between Box and ZoomInfo without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Box and ZoomInfo records are not retained after a sync operation.
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 427 integrations available for Box and ZoomInfo.
Popular · 7 of 427
-
Box ⇄ Kommo -
Box ⇄ Kustomer -
Box ⇄ Nimble -
Box ⇄ Nutshell -
ZoomInfo ⇄ Sharepoint -
ZoomInfo ⇄ Egnyte -
ZoomInfo ⇄ Amazon S3
No integrations match .
