Real-time
Two-way sync
Changes in Box or Folk CRM instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Folk CRM integration — real-time, two-way sync
Keep Box and Folk 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 Folk CRM
Keep the paperwork with the relationship: Folk CRM and Box share every customer's records and files in real time, in both directions.
Folk 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 Groups, Custom fields, Notes, Reminders in Folk CRM aligned with Tasks, Events, Files, Folders 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 Folk CRM; and records from Folk 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 Keep folk and a billing or customer success tool aligned on company records as deals close.
- 02 Sync folk people and companies with a marketing or outbound tool so outreach lists stay current.
- 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
Documents linked back to the record
A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Folk CRM, so the customer's paperwork sits with the relationship instead of a shared drive.
CRM records archived into storage
Records from Folk 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 Folk CRM, so people working the account see where the paperwork stands without opening storage.
What you can sync between Box and Folk 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 | Folk CRM objects | How this pairing syncs | |
|---|---|---|---|
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Events is specific to Box and Custom fields to Folk 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. | Notes Free-text context attached to people and companies, readable for reporting. | Files is specific to Box and Notes to Folk CRM — 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. | Reminders Follow-up items that can be created from external triggers. | Folders is specific to Box and Reminders to Folk CRM — 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. | People Contact records; the primary entity synced with outreach and enrichment tools. | Metadata is specific to Box and People to Folk CRM — 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. | Companies Organization records linked to people and kept aligned with billing or CS systems. | Collaborations is specific to Box and Companies to Folk CRM — each maps to any object or custom field on the other side. |
How changes propagate between Box and Folk 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 Folk 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Folk CRM Box Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
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.
- Folk CRM: Subject to the platform's API rate limits.
What ships with Box ⇄ Folk CRM
Connect Box and Folk CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Folk CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Folk 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 Folk CRM record.
Observability
Monitoring
Track your Box ⇄ Folk 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 Folk CRM.
How the Box and Folk 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.
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Box to Folk 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 Folk 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
Folk CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Folk 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 ⇄ Folk 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 Folk CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Folk CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Folk CRM: authenticate both systems, choose the objects to sync (such as Box's Groups and Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Box and Folk CRM: Documents linked back to the record; CRM records archived into storage; Document status on the record. A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Folk CRM, so the customer's paperwork sits with the relationship instead of a shared drive.
-
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. Folk CRM: REST API. Authentication: API key (Bearer token). Stacksync manages authentication, retries, and rate limits on both sides.
-
Folk CRM: Custom fields are defined per group, which means field mappings can differ across groups within the same workspace. 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 Folk 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 Folk 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 Folk CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Folk CRM integration in-house.
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 407 integrations available for Box and Folk CRM.
Popular · 6 of 407
-
Box ⇄ Salesloft -
Box ⇄ SAP Sales Cloud -
Box ⇄ Streak CRM -
Folk CRM ⇄ Amazon S3 -
Folk CRM ⇄ Sharepoint -
Folk CRM ⇄ Egnyte
No integrations match .
