Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Inbound JSON feeds are validated, reshaped and delivered into SolidWorks records, so supplier and configurator data reaches engineering as structured input rather than as email attachments.
Engineering receives structured data constantly: component specifications from suppliers, option selections from a configurator, dimensional data from a customer portal. It arrives as JSON nobody can use directly, so an engineer retypes the values into SolidWorks properties, or writes a script that works until the payload changes shape. A JSON to SolidWorks integration through Alumio puts a governed layer in between: payloads are validated against expected fields, units and identifiers are normalised, and only conforming data reaches engineering records.
DATA THAT FLOWS BETWEEN THEM
Component specifications
Configurator selections
Custom properties
Material data
Dimensional values
Validation results
Incoming JSON is checked against expected fields and units before it reaches SolidWorks, so a malformed feed is rejected rather than becoming a part modelled to wrong values.
Supplier and configurator values are written into SolidWorks properties directly, which removes the transcription step where a decimal place quietly becomes a manufacturing error.
Mapping lives in Alumio rather than in a one-off script, so a supplier changing their payload is a configuration update instead of an emergency for whoever wrote the parser.
Each inbound message is logged with its content and its validation result, so an engineering query about where a value came from has an answer rather than a shrug.
A supplier sends component data as JSON, Alumio validates and normalises it, and the values are written into the matching SolidWorks custom properties, so engineering models against the current published specification.
Option selections captured by a web configurator arrive as JSON and are mapped to the parameters SolidWorks expects, so a made-to-order request reaches engineering as structured input rather than as a description in a notes field.
When an inbound payload is missing a required field or carries a mismatched unit, Alumio holds it and raises the exception, so the feed is corrected at source rather than producing a record that looks complete.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
More can be connected, and a PLM or ERP system is the usual next step, because once inbound data is validated it is worth landing in more than one place. Alumio delivers the same governed payload to each, so a supplier specification updates engineering records and the item master together instead of being processed twice with two chances to diverge.
Yes. JSON is on Alumio's published list of supported formats, so payloads are received, validated and reshaped in the flow, then written to SolidWorks through its available interface. Processing runs on arrival rather than on a schedule, which matters when a configurator selection is meant to reach engineering while the customer is still on the phone.
Field mapping, validation rules and unit normalisation are configured in Alumio, which is the point of doing it this way rather than maintaining the one-off parser scripts these feeds usually accumulate. Payload structures from suppliers can be genuinely awkward, and where a nested or inconsistent structure needs unpicking, the Code Transformer accepts custom JavaScript for that transformation alone.
Only if something validates it first. A feed will happily deliver a renamed field, a missing tolerance or a unit in the wrong system, and SolidWorks will accept whatever is written to it. Alumio applies the validation rules you define before anything lands, rejects what does not conform, and logs the reason. That is the difference between a feed that keeps records current and one that quietly corrupts them.
It is held rather than partially applied. Alumio logs the full payload, monitors the flow in real time, and alerts you the moment validation or the write is refused, showing the field at fault and the reason in one view. Automatic retries cover transient faults, and a payload that still cannot be processed stays queued with its content intact, so no supplier update goes missing unnoticed.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
