Integrations
A connection to your ERP with stated limits
A read-only REST API, outgoing webhooks, an inbound webhook for indicator readings and a registered Excel / CSV bridge; a company admin creates keys with permitted scopes. There is no ready-made SAP, Logo or Netsis connector; we say so before the quote.
- Outside connections off until the company enables them
- Webhook notifications are signed
- Faulty rows listed before import

Integrations screen
In short
Gemy talks to outside systems in six ways: a read-only REST API, outgoing webhooks, an inbound webhook for indicator readings, a registered Excel / CSV bridge, OIDC sign-in and SCIM user sync, e-mail and push notifications. There is no ready-made SAP, Logo or Netsis connector. None of the outside connections work until the company admin switches them on.
- The REST API only reads; there is no write API
- Outgoing webhook notifications are signed
- The inbound webhook accepts indicator readings only
- No ready-made SAP, Logo or Netsis connector
- OIDC and SCIM are switched on by the company admin
Six ways to connect
REST API (read)
Records, actions, indicators, units and people can be read; keys are created by a company admin with permitted scopes. There is no write API.
Outgoing webhooks
Signed notifications on events you pick (e.g. record approved).
Inbound webhook
Accepts indicator readings only (e.g. a daily value from a production system).
Excel / CSV bridge
Regular imports with registered templates; faulty rows are listed before import.
OIDC and SCIM (company enables)
Sign-in and user sync with your corporate identity provider.
E-mail and push
Your own SMTP server; browser / phone notifications.
Let's map what's possible for your ERP
We don't promise ready-made connectors; we listen to your IT team and work out together in a call what the API and webhooks make possible.