Real-time
Two-way sync
Changes in Box or Outreach instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Outreach integration — real-time, two-way sync
Keep Box and Outreach 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 Outreach
Keep the paperwork with the relationship: Outreach and Box share every customer's records and files in real time, in both directions.
Outreach 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 Users, Mailboxes, Prospects, Accounts in Outreach 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 Outreach; and records from Outreach 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 Suppress prospects across systems when a contact unsubscribes or a customer churns.
- 02 Enroll leads in sequences automatically by writing sequence-state records when a lead crosses a scoring threshold in the warehouse.
- 03 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
- 04 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.
Common sync patterns
CRM records archived into storage
Records from Outreach 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 Outreach, 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 Outreach 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.
What you can sync between Box and Outreach
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 | Outreach 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. | Users Seat holders used to resolve ownership on synced records | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Tasks Rep action items mirrored between Outreach and the CRM | 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. | Sequence states Per-prospect enrollments; writing one adds a prospect to a cadence | Events is specific to Box and Sequence states to Outreach — 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. | Mailings Sent emails with engagement data, pulled for activity analytics | Files is specific to Box and Mailings to Outreach — 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. | Calls Logged call records synced into engagement reporting | Folders is specific to Box and Calls to Outreach — 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. | Opportunities Deal records used to tie engagement to pipeline outcomes | Metadata is specific to Box and Opportunities to Outreach — each maps to any object or custom field on the other side. |
How changes propagate between Box and Outreach
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 Outreach 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 Outreach through its API, with automatic retries and rate-limit backoff.
Outreach Box Sub-second propagation
DetectionOutreach notifies Stacksync of record changes through webhook events. Webhook subscriptions on resource create, update, and destroy events, plus polling.
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.
- Outreach: Subject to per-user hourly rate limits.
What ships with Box ⇄ Outreach
Connect Box and Outreach for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Outreach connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Outreach 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 Outreach record.
Observability
Monitoring
Track your Box ⇄ Outreach 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 Outreach.
How the Box and Outreach 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.
Outreach
- Integration surface
- REST API conforming to the JSON:API specification
- Authentication
- OAuth 2.0
- Change detection
- webhook subscriptions on resource create, update, and destroy events, plus polling
- Capabilities
- read · write · webhooks
- Rate limits
- subject to per-user hourly rate limits
How it works
How to connect Box to Outreach — 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 Outreach 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
Outreach
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Outreach 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 ⇄ OutreachCustomers 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 OutreachCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Outreach integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Outreach: authenticate both systems, choose the objects to sync (such as Box's Users and Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Outreach: CRM records archived into storage; Document status on the record; One place for a customer's files. Records from Outreach 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.
-
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. Outreach: REST API conforming to the JSON:API specification. Authentication: OAuth 2.0. Stacksync manages authentication, retries, and rate limits on both sides.
-
Outreach: Webhook subscriptions can be registered per resource for create, update, and destroy events, enabling near-real-time outbound sync. 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 Outreach 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 Outreach records are not retained after a sync operation.
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 490 integrations available for Box and Outreach.
Popular · 7 of 490
-
Box ⇄ SAP Sales Cloud -
Box ⇄ Streak CRM -
Box ⇄ SugarCRM -
Box ⇄ Twenty CRM -
Outreach ⇄ Amazon S3 -
Outreach ⇄ Sharepoint -
Outreach ⇄ Egnyte
No integrations match .
