Real-time
Two-way sync
Changes in Box or Freshworks CRM instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Freshworks CRM integration — real-time, two-way sync
Keep Box and Freshworks 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 Freshworks CRM
Keep the paperwork with the relationship: Freshworks CRM and Box share every customer's records and files in real time, in both directions.
Freshworks 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 Contacts, Accounts, Deals, Tasks in Freshworks CRM aligned with Events, Files, Folders, Metadata 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 Freshworks CRM; and records from Freshworks 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 deal and activity data into a Postgres database that internal tools query directly.
- 02 Sync unified contact records, covering sales and marketing attributes, into a warehouse for full-funnel reporting.
- 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 Freshworks CRM, 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 Freshworks CRM, so the customer's paperwork sits with the relationship instead of a shared drive.
CRM records archived into storage
Records from Freshworks 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.
What you can sync between Box and Freshworks 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 | Freshworks 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 Follow-ups created from external signals such as product usage events. | 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. | Accounts Company records kept consistent with ERP and billing systems. | Collaborations is specific to Box and Accounts to Freshworks 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. | Deals Pipeline records synced out for forecasting and full-funnel reporting. | Users is specific to Box and Deals to Freshworks 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. | Appointments Meeting records readable for activity reporting. | Groups is specific to Box and Appointments to Freshworks 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. | Sales activities Logged activity types used in engagement and productivity analysis. | Events is specific to Box and Sales activities to Freshworks 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. | Lists Contact list membership synced against segments computed in a warehouse. | Files is specific to Box and Lists to Freshworks CRM — each maps to any object or custom field on the other side. |
How changes propagate between Box and Freshworks 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 Freshworks 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 Freshworks CRM through its API, with automatic retries and rate-limit backoff.
Freshworks CRM Box Sub-second propagation
DetectionFreshworks CRM notifies Stacksync of record changes through webhook events. Polling with updated-at filters.
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.
- Freshworks CRM: Subject to per-account API rate limits that vary by plan.
What ships with Box ⇄ Freshworks CRM
Connect Box and Freshworks CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Freshworks CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Freshworks 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 Freshworks CRM record.
Observability
Monitoring
Track your Box ⇄ Freshworks 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 Freshworks CRM.
How the Box and Freshworks 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.
Freshworks CRM
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters; outbound webhooks can be configured through workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by plan
How it works
How to connect Box to Freshworks 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 Freshworks 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
Freshworks CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Freshworks 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 ⇄ Freshworks 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 Freshworks CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Freshworks CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Freshworks 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.
-
Freshworks CRM: Contacts and accounts expose lifecycle stages and custom fields through the API, so one record serves both sales and marketing workflows. Box: Files and folders share the Box ID namespace but are distinct object types; the account root is always folder ID 0. Stacksync's field mapping accounts for these differences between Box and Freshworks CRM 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 Freshworks CRM records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Freshworks CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Freshworks CRM integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Freshworks CRM. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Box: 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. On Freshworks CRM: Polling with updated-at filters; outbound webhooks can be configured through workflow automations. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 513 integrations available for Box and Freshworks CRM.
Popular · 7 of 513
-
Box ⇄ Gorgias -
Box ⇄ Infor CRM -
Box ⇄ Insightly -
Box ⇄ Intercom -
Freshworks CRM ⇄ Sharepoint -
Freshworks CRM ⇄ Egnyte -
Freshworks CRM ⇄ Amazon S3
No integrations match .
