The secure, stable connection to your Isah environment.
erpconnect.red gives applications, dashboards and AI agents controlled access to Isah through stored procedures, without exposing your database directly.
Custom build, third-party, AI agent or dashboard
Stored procedures
One connection, three questions
Is it quick to implement and easy to manage?
A ready-made API layer instead of custom work for every integration. Less project risk, predictable lead time.
View use cases →Does our Isah environment stay secure?
Per clientId you decide which stored procedures, from which IP addresses and with which database user. Every request is logged.
Go to security →What does my application talk to?
A documented interface with Swagger. GET to retrieve, POST to process. Works for AI-generated code too.
Go to documentation →Where erpconnect.red makes the difference
Connecting AI-generated applications to Isah
Teams use AI tools to build their own apps, chatbots and dashboards in days, and those need Isah data.
Direct database access from quickly built code: broad permissions, unknown queries, no oversight.
The app only talks to erpconnect.red and can only run the stored procedures that have been released.
Teams keep building fast, while IT stays in control of what happens in Isah.
Customer portals and dashboards
Real-time insight into orders, stock or planning from Isah, in your own web application.
Read the use case →External applications
E-commerce, CRM, planning or BI tools that need Isah data, without a direct database connection.
Read the use case →Process automation
Workflow tools or AI agents that read or write Isah data through stored procedures.
Read the use case →Reporting and AI analysis
Isah data safely available for analysis and forecasting, without exposing the database.
Read the use case →Stored procedures as an API
erpconnect.red executes stored procedures and expects their input parameters as data. Once executed, the result is returned.
- 00AuthenticateYour application signs in with a clientId and clientSecret and receives a bearer token.
- 01CallGET to retrieve data, POST to process or change data.
- 02Executeerpconnect.red checks permissions and runs the stored procedure on Isah.
- 03ResultThe output of the stored procedure is returned to your application.
How do we keep this secure and manageable?
The first question when a developer wants to "connect something AI to Isah". Per clientId you configure:
Swagger per API, logging per request
Released stored procedures are included in (Swagger) documentation that can be switched on or off per API. We advise publishing it on an externally reachable endpoint.
Request documentation accessOne-off licence, yearly support
Start with a conversation
Request a clientId, book an intake or discuss a specific (AI) use case with us.