Real-time
Two-way sync
Changes in Box or Pipedrive instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Pipedrive integration — real-time, two-way sync
Keep Box and Pipedrive 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 Pipedrive
Keep the paperwork with the relationship: Pipedrive and Box share every customer's records and files in real time, in both directions.
Pipedrive 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 Pipelines, Deals, Persons, Organizations in Pipedrive aligned with Users, Groups, Tasks, Events 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 Pipedrive; and records from Pipedrive 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 Sync deals, persons, and organizations to a database for reporting beyond the built-in Insights views.
- 02 Write enrichment or product usage data into Pipedrive custom fields so reps prioritize with live signals.
- 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
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 Pipedrive, 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 Pipedrive 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 Pipedrive, 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 Pipedrive
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 | Pipedrive objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Files Synced with incremental and full sync per the Stacksync docs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Pipelines Synced with incremental and full sync per the Stacksync docs. | Metadata is specific to Box and Pipelines to Pipedrive — 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. | Deals Pipeline records with stage and value; the primary object for reporting and win-triggered automation. | Collaborations is specific to Box and Deals to Pipedrive — 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. | Persons Contact records; synced with marketing tools and enriched from external data. | Users is specific to Box and Persons to Pipedrive — 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. | Organizations Company records linked to persons and deals; matched to billing customers. | Groups is specific to Box and Organizations to Pipedrive — 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. | Activities Calls, meetings, and tasks; read out for rep activity reporting. | Tasks is specific to Box and Activities to Pipedrive — each maps to any object or custom field on the other side. |
How changes propagate between Box and Pipedrive
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 Pipedrive 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 Pipedrive through its API, with automatic retries and rate-limit backoff.
Pipedrive Box Sub-second propagation
DetectionPipedrive notifies Stacksync of record changes through webhook events. Webhooks on per-object create, update, and delete events, with polling on 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.
- Pipedrive: Request budgets vary by plan and authentication method.
What ships with Box ⇄ Pipedrive
Connect Box and Pipedrive for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Pipedrive connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Pipedrive 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 Pipedrive record.
Observability
Monitoring
Track your Box ⇄ Pipedrive 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 Pipedrive.
How the Box and Pipedrive 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.
Pipedrive
- Integration surface
- REST API
- Authentication
- No-code guided connection: create a connection, select Pipedrive, then click "Allow and Install" (OAuth-style app install; docs do not name the protocol)
- Change detection
- Webhooks on per-object create, update, and delete events, with polling on update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Request budgets vary by plan and authentication method.
How it works
How to connect Box to Pipedrive — 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 Pipedrive 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
Pipedrive
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Pipedrive 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 ⇄ PipedriveCustomers 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 PipedriveCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Pipedrive integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Pipedrive: authenticate both systems, choose the objects to sync (such as Box's Files and Metadata), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Pipedrive: Webhooks on per-object create, update, and delete events, with polling on update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Pipedrive side: Pipelines, Deals, Persons, Organizations, plus custom fields where Pipedrive exposes them. On the Box side: Users, Groups, Tasks, Events. 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 Pipedrive: 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 Pipedrive, 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. Pipedrive: REST API. Authentication: No-code guided connection: create a connection, select Pipedrive, then click "Allow and Install" (OAuth-style app install; docs do not name the protocol). Stacksync manages authentication, retries, and rate limits on both sides.
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 514 integrations available for Box and Pipedrive.
Popular · 7 of 514
-
Box ⇄ Streak CRM -
Box ⇄ SugarCRM -
Box ⇄ Twenty CRM -
Box ⇄ Veeva CRM -
Pipedrive ⇄ Egnyte -
Pipedrive ⇄ Amazon S3 -
Pipedrive ⇄ Sharepoint
No integrations match .
