Your systems can work together. SmartWorx makes the connection.
Use other systems’ information and capabilities. Let applications and partners connect to SmartWorx with access you control. Keep organizations informed by sharing the right information as it changes.
Put other systems’ capabilities to work.
When another system provides an API—a way for software to communicate—SmartWorx can connect directly. You don’t have to wait for a product-specific connector or buy a separate integration platform.
Let AI help discover what’s available and interpret documentation, import the system’s API definition, or configure the connection yourself. Then use its information and supported actions in your SmartWorx applications and workflows.
Get information
Look up stock, customer details, or an order’s status.
Take action
Create an order or update information in another system.
Respond to events
Receive a webhook—an event notification—and trigger a workflow.
Receive completed results
Handle a callback when an earlier request finishes.
Example
From stock check to shipment update.
SmartWorxYour configured workflow
Supplier’s APIExternal system
Request · Filter kit A
Response · 24 units available
Order · 6 filter kits
Supplier event · Shipment dispatched
Delivery updated · Team notified
Follow both directions: SmartWorx requests information and takes action; the supplier can also initiate an update.
Authorize and testReview the operations, access and expected results.
Use in your workflowsPut the configured connection to work.
Import their API definition. The external system’s published API determines the operations and protocols available. Authorize, review and test the connection before use.
Give every connection exactly the access it needs.
Let applications and partners work with your SmartWorx information under permissions you define. Choose the records, fields, and actions each connection can access. SmartWorx automatically generates an OpenAPI definition for that connection. SmartWorx limits each connection to the information and actions you authorize.
The API definition tells the other application how to connect and which operations are available to it.
Automatically generate your API definition for them. You choose the access. SmartWorx creates the definition.
Example
One platform. Different permitted views.
You choose the access
This supplier’s assigned orders
Can readOrder numberItemQuantity
Can updateExpected deliveryDelivery status
Kept privateOther suppliers’ orders and internal financial details
Automatically generated
OpenAPI
Supplier API definition
How to connect. Which operations and fields are available.
Generated by SmartWorx from the access you assign.
Supplier applicationStarts the request
Read assigned ordersOnly permitted information
SmartWorxAccess limited by assigned permissions
Permitted responseOrder PO-1042 · Filter kit A · 6 units
You choose the access. SmartWorx generates the API definition and limits the connection to the permitted records, fields, and actions.
Tell other systems when something happens.
Choose an event, set the conditions, and select the information to send. SmartWorx notifies the destination when that event occurs.
ExampleSent by SmartWorx
EventWork order completed
ConditionApproved for billing
Selected informationWork order, customer reference, approved total
DestinationBilling system
Incoming: another system tells SmartWorx; a workflow responds.Outgoing: SmartWorx tells another system about an event.
Share what matters. Control what stays private.
Keep connected organizations up to date while deciding exactly what each one can see and change.
Share selected records and fields, transform information before it is sent, and give each organization the access it needs. One organization might receive a read-only update. Another might be allowed to update specific information.
Connect organizations directly or coordinate sharing through a central hub. Each connection can have its own rules for what moves in either direction.
Select what to shareChoose the relevant records and fields.
Shape what others receiveMap fields, transform values or mask identifiers before sending.
Control changesAllow read-only access or updates to selected fields.
Coordinate every connectionSet different rules for each organization and each direction.
Example
Aircraft coordination, with separate sharing rules.
Aircraft operations
Own SmartWorx environment
Aircraft reference
AX-204
Model
Utility aircraft
Maintenance status
Ready for service
Stays in this environmentCrew details · internal costs · operational notes
Selected fields
Sharing hubDifferent fields. Different permissions. Different destinations.
Permitted maintenance update
Selected sharing arrangement
Planning organization
Current shared value: Available
Receives
Aircraft reference
Availability
Can update
Read-only
Kept private
Detailed maintenance status, crew details and internal costs
A simpler view for Planning“Ready for service”“Available”The mapping sends availability, not the detailed internal status.
Select an organization to inspect its access, or play the two-way sharing example. Private information stays at the source.
The return connection permits maintenance changes only. Sharing that new status onward follows each destination’s configured rules.
Live sharing through WebSocket connections, governed by SmartWorx permissions, mappings, and sharing rules. WebSockets provide the channel; SmartWorx controls what is shared.
Keep connections understandable and under control.
Know who connects, what they can access, and what happened when a connection ran. Review activity, investigate errors, and keep mappings and permissions aligned as systems change.
SmartWorxYour configured workflow