React when trade happens.
Start work when an order is created, paid, prepared, collected, refunded, or cancelled.
Turn commerce activity into work that moves.
Connect orders, customers, stock, and payment events to the business tools merchants and institution teams already use.
Start with real commerce
Every useful flow begins with a record the merchant already created.
Connect listens to activity inside the deployment. It does not invent another customer list, order store, or reporting system that must later be reconciled.
Keep customer records connected.
Use customer activity and consent captured through the merchant’s own commerce surfaces.
Bring exceptions into view.
Route stock, fulfilment, payment, and location signals to the team responsible for acting.
One visible workflow
Choose, map, test, run.
Template
Start from a proven pattern.
Choose a commerce pattern, then adapt its conditions and destination for each merchant.
Mapping
Move only the fields the action needs.
Show the source record, selected conditions, destination fields, and provider boundary before anything is activated.
Test
Preview the route with a known record.
Confirm what each step receives and produces without sending live merchant data into an unfinished workflow.
Run history
Automation should never become invisible.
Inspect completed, waiting, and failed steps with a path back to the source record that started the run.
Business applications
Connect to the tools merchants already run.
Institutions can package approved connector implementations for communication, productivity, accounting, marketing, and commerce services.
WhatsApp BusinessMessaging
Microsoft 365Productivity
Google WorkspaceProductivity
SlackTeam communication
QuickBooksAccounting
XeroAccounting
MailchimpMarketing
HubSpotCustomer operations
ShopifyCommerce
ZapierAutomation
These are illustrative connector targets, not a claim that every integration ships with Box. A connection exists only when an approved implementation is installed in the institution’s deployment.
Useful in context
Different businesses need different work to move.
Food and hospitality
Send paid orders to the team preparing them.
Route fulfilment details without turning the destination app into another order system.
Retail
Raise a task before stock becomes a missed sale.
Use catalogue and inventory events so the right team can replenish before stock becomes a missed sale.
Professional services
Keep customer follow-up attached to completed work.
Create approved messages or tasks from bookings, invoices, and customer activity.
Online commerce
Coordinate fulfilment across the tools already in place.
Pass only the order details that delivery, support, or accounting tools need.
Operational insight
Read the automation beside the trade that produced it.
Run history stays attached to source records. Teams can see what happened, where work stopped, and whether the destination accepted the action.
Explore Insights
The boundary stays visible
A connector moves approved work. It does not move ownership.
Installed deliberately
Only connector packages included and configured by the institution exist in the deployment.
Scoped explicitly
Each flow exposes the records and fields it needs rather than granting broad access by default.
Operated visibly
Tests, runs, failures, and destination responses remain available to the teams responsible.
Package model
Connect is installed, not merely switched on.
The Connect package supplies templates, the flow builder, run history, and connector boundaries. Specific destination implementations are added only when the institution chooses to support and operate them.
See the architectureConnect
Questions.
Does Box include every logo shown above?
No. They are examples of widely used business applications that an institution may choose to support through approved connector implementations.
Can an institution build its own connector?
Yes. Connector packages can target institution services or third-party applications through bounded APIs and explicit record mappings.
Where do merchants manage flows?
Templates, configuration, tests, and run history live inside Merchant Console under the institution’s brand and permissions.
Does Connect copy the whole commerce database?
No. A flow receives the records and fields required for its configured action. The Box deployment remains the source of commerce truth.
What happens when a destination is unavailable?
The run remains visible with its current state and destination response so the responsible team can investigate or retry according to its operating policy.
Box Connect