AlisQI API
The AlisQI API allows any developer to read and write all master and transactional data. The endpoints of our API support our dynamic data model. This enables you or any developer you hire, to create custom integrations with your self-defined AlisQI setup.
Read all about the AlisQI API here
To connect services, transform data or schedule operations, we suggest you use a middleware tool. Otherwise, you’ll find yourself building custom integrations for each and every tool you deploy.
If you already use Microsoft 365 or Azure services, you might want to evaluate Microsoft Power Automate.
Microsoft Power Automate
Microsoft Power Automate is a tool that helps you automate manual processes without the need to write code. It allows users to build workflows (“Flows”) that connect apps and services, automate actions, and move data between systems.
To understand how Power Automate works, you need to know what an API is. An API (application programming interface) is something that a software provider (like AlisQI) provides so developers can access data within their applications. For example, a developer writes code that detects all new sensor data from an instrument and writes that to AlisQI.
Instead of needing to write code for every API, Power Automate provides a large library of pre-built connectors and actions. These connectors can be combined using a low-code visual workflow editor.
Once set up, Power Automate can run continuously or be triggered by events (such as a new record being created, a scheduled time, or an approval being completed), enabling automation with minimal maintenance.
Native AlisQI connector
AlisQI is available as a native connector within the Microsoft Power Automate platform.
This means you can easily connect AlisQI to other Microsoft services (such as Outlook, SharePoint, Teams, Excel, and Dynamics 365) as well as hundreds of third-party applications available in the Power Platform ecosystem.
Trigger a Power Automate flow from AlisQI
You can also trigger Microsoft Power Automate flows directly from AlisQI. A common approach is to create a Flow in Power Automate using an HTTP trigger (for example: “When an HTTP request is received”), which provides a unique endpoint URL. This URL can then be called from an AlisQI workflow using a webhook call (typically a POST request with a JSON payload). By including key context in the payload, such as the result values, you can let Power Automate continue the process outside AlisQI, for example by updating a batch status in ERP or sending a Teams message.
Security
Any system integration deals with your important data. And thus, its security should be validated.
All AlisQI API calls are subject to encryption and authentication. All API calls are sent over HTTPS, securing the data transfer. In order to invoke the AlisQI API endpoints, developers need to create an authentication token. Each token is connected to a single user. The READ/WRITE permissions this user has for analysis-sets (via its user group), also apply to the API invocations.
When deploying a middleware solution, being it Power Automate or any other platform, that platform will process your data and should thus be secured as well.
Microsoft provides extensive compliance, security, and governance capabilities across the Power Platform. However, you need to do your own assessments. To support your assessment, we recommend reviewing Microsoft’s official documentation on: