Real-time
Two-way sync
Changes in Box or Infor LN instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ ERP
Box to Infor LN integration — real-time, two-way sync
Keep Box and Infor LN 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 Infor LN
Move the documents and data that Infor LN produces into Box as files, and let files stored in Box update the records they belong to in Infor LN, continuously and without exports or manual filing.
Infor LN runs the business on structured records: Bills of material, Business partners, Sales orders, Purchase orders. Box holds files and the metadata that describes them: Files, Folders, Metadata, Collaborations. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Infor LN touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Box, from signed contracts to vendor bills to receipts, describe a transaction Infor LN needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Bills of material, Business partners, Sales orders, Purchase orders in Infor LN and Files, Folders, Metadata, Collaborations in Box in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Box already labeled and filed, and metadata captured against a stored file can create or update the matching record in Infor LN. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Infor LN and the file in Box never describe two different versions of the same document.
Common use cases
- 01 Run a two-way sync of business partners between LN and a CRM so sales and manufacturing share account data.
- 02 Keep inventory positions aligned between LN and distribution or aftermarket service systems.
- 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
Metadata that files itself
Record fields from Infor LN, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Box, so storage stays organized without anyone tagging by hand.
Where Box captures inbound files: details reach the record
A contract, vendor bill, or receipt added to Box with its details can create or update the matching record in Infor LN, so a document captured outside the finance system still reaches the books.
An archive that stays current
As records change in Infor LN, the corresponding files and metadata in Box are kept in step, so a stored document reflects the latest version rather than a stale one-time export.
What you can sync between Box and Infor LN
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 | Infor LN 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. | Bills of material Product structures shared with engineering and planning tools. | Files is specific to Box and Bills of material to Infor LN — 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. | Business partners LN's unified customer/supplier records matched against CRM accounts. | Folders is specific to Box and Business partners to Infor LN — 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. | Sales orders Demand documents synced in from EDI and commerce channels. | Metadata is specific to Box and Sales orders to Infor LN — 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. | Purchase orders Supply documents shared with supplier and procurement systems. | Collaborations is specific to Box and Purchase orders to Infor LN — 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. | Production orders Shop-floor work orders synced with MES for execution visibility. | Users is specific to Box and Production orders to Infor LN — 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. | Warehouse / inventory Stock positions exposed so external channels reflect real availability. | Groups is specific to Box and Warehouse / inventory to Infor LN — each maps to any object or custom field on the other side. |
How changes propagate between Box and Infor LN
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 Infor LN 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 Infor LN through its API, with automatic retries and rate-limit backoff.
Infor LN Box Interval-based propagation
DetectionStacksync polls Infor LN for changes on an incremental schedule, reading only records changed since the previous pass. Event-style BOD publications through Infor ION where configured.
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.
- Infor LN: Subject to the ION API gateway's tenant rate limits in cloud deployments.
What ships with Box ⇄ Infor LN
Connect Box and Infor LN for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Infor LN connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Infor LN 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 Infor LN record.
Observability
Monitoring
Track your Box ⇄ Infor LN 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 Infor LN.
How the Box and Infor LN 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.
Infor LN
- Integration surface
- SOAP and REST web services, with standardized BOD exchange through Infor ION in Infor OS deployments
- Authentication
- OAuth 2.0 via the ION API gateway in cloud deployments; application credentials on premises
- Change detection
- Event-style BOD publications through Infor ION where configured; otherwise polling
- Capabilities
- read · write
- Rate limits
- Subject to the ION API gateway's tenant rate limits in cloud deployments.
How it works
How to connect Box to Infor LN — 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 Infor LN 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
Infor LN
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Infor LN 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 ⇄ Infor LNCustomers 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 Infor LNCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Infor LN integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Infor LN: authenticate both systems, choose the objects to sync (such as Box's Files and Folders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Infor LN side: Bills of material, Business partners, Sales orders, Purchase orders, plus custom fields where Infor LN exposes them. On the Box side: Files, Folders, Metadata, Collaborations. 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 Infor LN: Metadata that files itself; Where Box captures inbound files: details reach the record; An archive that stays current. Record fields from Infor LN, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Box, so storage stays organized without anyone tagging 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. Infor LN: SOAP and REST web services, with standardized BOD exchange through Infor ION in Infor OS deployments. Authentication: OAuth 2.0 via the ION API gateway in cloud deployments; application credentials on premises. Stacksync manages authentication, retries, and rate limits on both sides.
-
Infor LN: LN's multi-company and multi-site structure partitions core data, so syncs must be scoped to the right company and site context. Box: The user Events API is consumed with a stream_position and long-polling; enterprise/admin events retain roughly one year of history and can lag strict ordering for near-real-time reads. Stacksync's field mapping accounts for these differences between Box and Infor LN without custom code.
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 496 integrations available for Box and Infor LN.
Popular · 7 of 496
-
Box ⇄ SuiteAnalytics -
Box ⇄ Dynamics 365 Business Central -
Box ⇄ SAP Business ByDesign -
Box ⇄ SAP Business One -
Infor LN ⇄ Sharepoint -
Infor LN ⇄ Egnyte -
Infor LN ⇄ Amazon S3
No integrations match .
