Real-time
Two-way sync
Changes in Box or Freshsales instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Freshsales integration — real-time, two-way sync
Keep Box and Freshsales 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 Freshsales
Keep the paperwork with the relationship: Freshsales and Box share every customer's records and files in real time, in both directions.
Freshsales 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 Tasks, Appointments, Notes, Sales activities in Freshsales aligned with Folders, Metadata, Collaborations, Users 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 Freshsales; and records from Freshsales 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 Two-way sync of contacts and accounts between Freshsales and a Postgres database so product and data teams query CRM data with SQL.
- 02 Sync deals into a data warehouse for pipeline reporting alongside product usage data.
- 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 Freshsales, 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 Freshsales, so the customer's paperwork sits with the relationship instead of a shared drive.
CRM records archived into storage
Records from Freshsales 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 Freshsales
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 | Freshsales 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 Rep to-dos created from external triggers or synced for productivity reporting. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Products Catalog items attached to deals for line-level revenue data. | Groups is specific to Box and Products to Freshsales — 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. | Contacts Person records carrying lifecycle stages; the main entity for two-way CRM syncs. | Events is specific to Box and Contacts to Freshsales — 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. | Accounts Company records kept aligned with billing, ERP, and warehouse tables. | Files is specific to Box and Accounts to Freshsales — 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. | Deals Pipeline records synced to a warehouse for revenue reporting. | Folders is specific to Box and Deals to Freshsales — 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. | Appointments Scheduled meetings readable for activity analytics. | Metadata is specific to Box and Appointments to Freshsales — each maps to any object or custom field on the other side. |
How changes propagate between Box and Freshsales
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 Freshsales 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 Freshsales through its API, with automatic retries and rate-limit backoff.
Freshsales Box Sub-second propagation
DetectionFreshsales notifies Stacksync of record changes through webhook events. Polling with updated-at filters through views.
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.
- Freshsales: Subject to per-account API rate limits that vary by Freshworks plan.
What ships with Box ⇄ Freshsales
Connect Box and Freshsales for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Freshsales connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Freshsales 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 Freshsales record.
Observability
Monitoring
Track your Box ⇄ Freshsales 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 Freshsales.
How the Box and Freshsales 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.
Freshsales
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by Freshworks plan
How it works
How to connect Box to Freshsales — 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 Freshsales 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
Freshsales
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Freshsales 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 ⇄ FreshsalesCustomers 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 FreshsalesCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Freshsales integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Freshsales: authenticate both systems, choose the objects to sync (such as Box's Tasks and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Freshsales: REST API. Authentication: API key sent as a Token authorization header. Stacksync manages authentication, retries, and rate limits on both sides.
-
Freshsales: List access runs through views (saved filters): the API returns contacts or deals per view, which shapes how full extracts and incremental pulls are structured. Box: Webhooks are capped per application and per file/folder target, must be verified with Box's signature keys, and their payloads carry the object reference rather than the full changed content. Stacksync's field mapping accounts for these differences between Box and Freshsales 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 Freshsales records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Freshsales connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Freshsales integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Freshsales. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Freshsales.
Popular · 7 of 513
-
Box ⇄ Streak CRM -
Box ⇄ SugarCRM -
Box ⇄ Twenty CRM -
Box ⇄ Veeva CRM -
Freshsales ⇄ Egnyte -
Freshsales ⇄ Amazon S3 -
Freshsales ⇄ Sharepoint
No integrations match .
