Connect what you already run

The cards below are examples of what teams move in and out, not the whole list. The API covers the platform: what the app can do, an integration can do too, within the permissions of the key it uses.

• Machine data in

  Readings from a gateway, a controller or another system land on the tracked values of a device and drive Rules.

• Work in

  Another system raises a job in Mesonify, with the same fields a person would fill in by hand.

• Stock moves in

  Issue or book in parts, by count or by serial number, so the shelf matches reality without anyone typing it twice.

• Assets in

  Your ERP or asset master owns the equipment list. Create devices and keep names, locations and serial numbers in step, so both sides hold the same register.

• Production orders in

  Your ERP or planning system dispatches an order to the floor: what to make, how many, by when and on which line.

• Live output in

  Counts and stop reasons from the line or its controller, so output and downtime come from the machine rather than from a tally sheet.

• Work out

  Read jobs back with their state, times, costs and the parts they used, into your own reporting or a data warehouse.

• Numbers out

  Stock on hand against its minimums, and the maintenance figures behind the dashboard, straight into Power BI or whatever you report in.

• Condition out

  Pull the history of a tracked value, vibration, temperature or pressure, into your own trending or a predictive model.

Every call is authenticated with an API key generated in the app, and each key carries its own permissions. Need a flow the cards do not show? Tell us what should move and we will tell you what it takes.