How is an integration platform different from a plain API?

A plain API is a single data-exchange endpoint that you have to build and maintain. An integration platform gives you a ready-made skeleton: triggers, authorization, transformations, system calls and logging – and you build the logic as a clear workflow instead of scattered code. The result is easier to maintain, auditable and faster to change.

Do I need to be a programmer to build an integration?

Most workflows are built from ready-made steps on the canvas – parsing, conditions, loops, SQL queries, HTTP calls or e-mail. When custom logic is needed, you can add a C# or JavaScript code step. A whole integration can also be imported from a single JSON file, which an AI agent can generate from documentation.

Where does the platform run – in the cloud or on our side?

The platform is self-hosted – you run it in your own infrastructure (on-premises or in your cloud). Data stays under your control and is not passed to third-party services, which matters for sensitive data and compliance requirements.

Which systems can I integrate with?

Any system that exposes HTTP/REST, a database (MS SQL, PostgreSQL) or a message queue. In practice we connect ERP and SAP, CMMS/MES systems, customer portals, data warehouses and queues such as Kafka. Both inbound and outbound authorization support Basic, API key, OAuth 2.0 and an external identity provider (OIDC).

How do I find out what went wrong in an integration?

Every request and every step is logged, and the integration run can be replayed on the canvas – you can see which step ran, with what input and result, and where an error occurred (e.g. the full database error message). This dramatically shortens diagnosis compared with digging through scattered logs.

Is the platform suitable for integrating with the SimplyMobile CMMS/MES?

Yes – the platform was built partly to connect our SimplyMobile systems (CMMS, MES, warehouse) with the client's systems, such as ERP or SAP, quickly and reliably. Thanks to ready-made steps and file-based import, deploying such an integration is fast and fully auditable.

Integration Platform – connect your systems without the chaos

Our integration platform ties together the systems that used to refuse to talk to each other – ERP, SAP, CMMS/MES, customer portals, databases and message queues. Instead of one-off scripts, you build clear, visual workflows: they receive data, transform it and deliver it where it belongs – with a full log of every step.

See the platform in action

A sample workflow: from an HTTP request, through transformation and logic, to a database write and a response.

Execution history

Kafka → BusinessPartner

d76d737f… · 296 ms

● Completed
Kafka → MPK

8b7f15e1… · 769 ms

● Completed
Kafka → BusinessPartner

35904b68… · 330 ms

● Completed
Kafka → MPK

14a84835… · 1.9 s

● Failed

Endpoints

POST /kafka/businesspartner ExternalOidc
POST /kafka/mpk ExternalOidc
POST /orders OAuth
GET /assets ApiKey

Step replay

trigger.http
action.parse

BusinessPartnerNumber, VatCode
action.sql

ext.SaveCompany
response

200 OK

Every step with its input, result and full error

What is an integration platform?

An integration platform is a middle layer that connects different systems and lets them exchange data in a controlled, repeatable way. It receives events (e.g. from an ERP, a portal or a message queue), transforms the data into the right format and passes it on – to a database, a CMMS/MES system, an external API or back to the source system. Instead of scattered, hard-to-maintain scripts, everything lives in one place – with a preview and full history of every flow.

Key capabilities

Visual workflows built on a canvas – no integration code scattered across the codebase
HTTP endpoints and timed (cron) triggers as the starting points of an integration
Request authorization: Basic, API key, OAuth 2.0 and an external identity provider (OIDC)
Workflow steps: data parsing, C#/JS code, conditions, loops over arrays, parallel branches
Calls to external APIs, SQL queries, e-mail sending and file export
Import a whole integration from a single JSON file – ready to be generated by AI agents
Full logging of every request and every step, with execution replay on the canvas

How does it work?

Every integration starts with a trigger – an incoming HTTP request or a timed schedule. From there, data flows through successive steps: it is parsed, enriched with your own code, checked against conditions and routed to the right systems. You can iterate over lists of records, run branches in parallel, and return a response immediately while finishing the rest of the work in the background.

As a result, a single source of events can save data to a database, notify an operator by e-mail and call an external system all at once – while you see exactly what happened, when and with what result.

Typical use cases

Syncing data between ERP/SAP and a CMMS/MES system (business partners, orders, assets)
Receiving events from a customer portal, storing them in a database and sending status callbacks
Consuming messages from queues (e.g. Kafka) and loading them into a database
Polling a system on a schedule and pushing changes to an external API (outbound integrations)
Generating and exporting files (e.g. XML / regulatory reports) from database data
Replacing fragile, one-off scripts with a single, auditable place

Security and full control

Self-hosted – the platform runs in your own infrastructure, data never leaves your organization
Secrets (passwords, connection strings, keys) are stored securely and never returned in responses
Every incoming request and every step goes to the log – full audit and diagnostics
Execution replay on the canvas cuts the time it takes to find the root cause of an error
Workflow versioning – every change is saved and can be rolled back

Contact Us

Need an app, consultation, or support for your CMMS/EAM maintenance systems?

FAQ – integration platform

How is an integration platform different from a plain API?

A plain API is a single data-exchange endpoint that you have to build and maintain. An integration platform gives you a ready-made skeleton: triggers, authorization, transformations, system calls and logging – and you build the logic as a clear workflow instead of scattered code. The result is easier to maintain, auditable and faster to change.
Do I need to be a programmer to build an integration?

Most workflows are built from ready-made steps on the canvas – parsing, conditions, loops, SQL queries, HTTP calls or e-mail. When custom logic is needed, you can add a C# or JavaScript code step. A whole integration can also be imported from a single JSON file, which an AI agent can generate from documentation.
Where does the platform run – in the cloud or on our side?

The platform is self-hosted – you run it in your own infrastructure (on-premises or in your cloud). Data stays under your control and is not passed to third-party services, which matters for sensitive data and compliance requirements.
Which systems can I integrate with?

Any system that exposes HTTP/REST, a database (MS SQL, PostgreSQL) or a message queue. In practice we connect ERP and SAP, CMMS/MES systems, customer portals, data warehouses and queues such as Kafka. Both inbound and outbound authorization support Basic, API key, OAuth 2.0 and an external identity provider (OIDC).
How do I find out what went wrong in an integration?

Every request and every step is logged, and the integration run can be replayed on the canvas – you can see which step ran, with what input and result, and where an error occurred (e.g. the full database error message). This dramatically shortens diagnosis compared with digging through scattered logs.
Is the platform suitable for integrating with the SimplyMobile CMMS/MES?

Yes – the platform was built partly to connect our SimplyMobile systems (CMMS, MES, warehouse) with the client's systems, such as ERP or SAP, quickly and reliably. Thanks to ready-made steps and file-based import, deploying such an integration is fast and fully auditable.