Real-time
Real-time sync
Changes in Box or Lusha instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Business productivity
Box to Lusha integration — real-time data sync
Keep Box and Lusha 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 Lusha
Land the records and documents that build up in Lusha into Box as they are created, and surface Box's file details on the Lusha records that point to them, without an export job to maintain.
Lusha is a read-only source: Stacksync reads its data in real time and delivers it into Box, so Box always reflects the current state of Lusha — without exports, scripts, or schedulers.
Lusha and Box hold different kinds of data. Lusha carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Box holds files and the metadata that describes them. Where the two meet is narrow but real: much of what Lusha produces has to be kept somewhere durable, and many of the files Box stores are the very documents Lusha's records point to.
Stacksync syncs Email Addresses, Phone Numbers, Prospecting Results, Bulk Enrichment Requests in Lusha with Collaborations, Users, Groups, Tasks in Box in real time. Records and attachments created in Lusha are written into Box as objects or files within seconds of being created. In the other direction, the metadata Box keeps about those files — name, location, owner, modified date — flows back onto the matching record in Lusha, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.
Common use cases
- 01 Build prospecting lists from Lusha search results and sync them into the CRM as leads.
- 02 Re-verify stale contact data on a schedule and flag records that no longer resolve.
- 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
A copy that outlives the tool
A continuously synced copy in Box preserves records and documents even as they age out of Lusha or get changed inside it, so history stays intact and reachable.
Feed a data lake or downstream pipeline
Structured records from Lusha land in Box as objects a data lake, search index, or processing pipeline can read, without a custom extract to build and babysit.
Archive what Lusha produces into Box
Records and events from Lusha — tickets, messages, orders, or issues — are written into Box as objects or files as they change, giving you a durable, addressable copy for retention and audit.
What you can sync between Box and Lusha
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 | Lusha objects | How this pairing syncs | |
|---|---|---|---|
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Bulk Enrichment Requests Batch lookups that enrich multiple records per request, used to backfill large contact lists rather than one-off calls. | Metadata is specific to Box and Bulk Enrichment Requests to Lusha — 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. | Person Profiles Contact-level enrichment results (work emails, phone numbers, title, company) returned per lookup. | Collaborations is specific to Box and Person Profiles to Lusha — 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. | Company Profiles Firmographic records (industry, size, location) appended to account or company rows. | Users is specific to Box and Company Profiles to Lusha — 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. | Email Addresses Work emails written into CRM contact fields during enrichment. | Groups is specific to Box and Email Addresses to Lusha — 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. | Phone Numbers Direct-dial and mobile numbers appended for outbound calling workflows. | Tasks is specific to Box and Phone Numbers to Lusha — 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. | Prospecting Results Search-based lists of people and companies matching filters, used to seed lead lists. | Events is specific to Box and Prospecting Results to Lusha — each maps to any object or custom field on the other side. |
How changes propagate between Box and Lusha
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 Lusha 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.
DeliveryLusha does not accept inbound record writes, so this direction carries requests rather than records: Lusha's output flows back as field updates on the originating Box records.
Lusha Box Interval-based propagation
DetectionStacksync polls Lusha for changes on an incremental schedule, reading only records changed since the previous pass. Data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change.
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.
- Lusha: Lookups consume credits and are subject to the platform's API rate limits.
What ships with Box ⇄ Lusha
Connect Box and Lusha for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Lusha connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Lusha 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 Lusha record.
Observability
Monitoring
Track your Box ⇄ Lusha 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 Lusha.
How the Box and Lusha 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.
Lusha
- Integration surface
- REST API
- Authentication
- API key
- Change detection
- Not event-driven; data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change
- Capabilities
- read
- Rate limits
- Lookups consume credits and are subject to the platform's API rate limits.
How it works
How to connect Box to Lusha — 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 Lusha 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
Lusha
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Lusha 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 ⇄ LushaCustomers 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 LushaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Lusha integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Box and Lusha — Lusha is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
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 Lusha records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Lusha connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Lusha integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Lusha. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
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 Lusha: Not event-driven; data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Lusha side: Email Addresses, Phone Numbers, Prospecting Results, Bulk Enrichment Requests, plus custom fields where Lusha exposes them. On the Box side: Collaborations, Users, Groups, Tasks. Stacksync auto-detects both schemas and converts types between the two systems.
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 366 integrations available for Box and Lusha.
Popular · 7 of 366
-
Box ⇄ Lemlist -
Box ⇄ Microsoft 365 -
Box ⇄ Microsoft Dynamics 365 -
Box ⇄ Microsoft Teams -
Lusha ⇄ Egnyte -
Lusha ⇄ Amazon S3 -
Lusha ⇄ Sharepoint
No integrations match .
