Skip to content
Storage ⇄ CRM

Box to HubSpot integration — real-time, two-way sync

Keep Box and HubSpot 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 HubSpot

Keep the paperwork with the relationship: HubSpot and Box share every customer's records and files in real time, in both directions.

HubSpot 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 Owner, Pipeline, Stages, Audit in HubSpot aligned with Files, Folders, Metadata, Collaborations 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 HubSpot; and records from HubSpot 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 Write warehouse-computed lead and account scores back to HubSpot properties on a schedule or in near real time.
  • 02 Sync HubSpot Tickets with an internal support database to unify service reporting across channels.
  • 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 HubSpot, 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 HubSpot 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 HubSpot, 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 HubSpot

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 HubSpot objects How this pairing syncs
Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. Deal Synced with incremental and full sync per the Stacksync docs. Users is specific to Box and Deal to HubSpot — 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. Line Item Synced with incremental and full sync per the Stacksync docs. Groups is specific to Box and Line Item to HubSpot — 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. Product Synced with incremental and full sync per the Stacksync docs. Tasks is specific to Box and Product to HubSpot — 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. Ticket Synced with incremental and full sync per the Stacksync docs. Events is specific to Box and Ticket to HubSpot — 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. Quote Synced with incremental and full sync per the Stacksync docs. Files is specific to Box and Quote to HubSpot — 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. Goal Synced with incremental and full sync per the Stacksync docs. Folders is specific to Box and Goal to HubSpot — each maps to any object or custom field on the other side.

How changes propagate between Box and HubSpot

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 HubSpot 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 HubSpot through its API, with automatic retries and rate-limit backoff.

HubSpot Box Sub-second propagation

DetectionHubSpot pushes changes as they happen — webhook events backed by change data capture. Records: incremental near-real-time change tracking.

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.
  • HubSpot: Request limits vary by subscription tier and API type.
What ships with Box ⇄ HubSpot

Connect Box and HubSpot for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–HubSpot connection.

Real-time

Two-way sync

Changes in Box or HubSpot instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Box or HubSpot 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 HubSpot record.

Observability

Monitoring

Track your Box ⇄ HubSpot 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 HubSpot.

How the Box and HubSpot 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.

HubSpot

Integration surface
REST API (CRM v3)
Authentication
OAuth (choose HubSpot account and authorize Stacksync); requires a HubSpot 'Super Admin' to grant access; optional "Grant access to sensitive fields" checkbox for sensitive/highly sensitive fields
Change detection
Records: incremental near-real-time change tracking. Associations: HubSpot has no native association CDC
Capabilities
read · write · CDC · webhooks
Rate limits
Request limits vary by subscription tier and API type.
HubSpot setup guide
How it works

How to connect Box to HubSpot — 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.

  1. 01

    Connect your apps

    Authenticate Box and HubSpot with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Box connected
    HubSpot connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Box and HubSpot 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Box ⇄ HubSpot
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Box HubSpot
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Box and HubSpot integration FAQ

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 527 integrations available for Box and HubSpot.

Popular · 7 of 527
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.