Named operations
Prefer explicit business methods and allow-listed paths over an arbitrary user-selectable proxy.
Integrations
Telemetry that stops at a dashboard is only half an operation.
Connect approved monitoring evidence to the system and team responsible for the next decision—without claiming every connector is already built.
Current position
Built in where we own the record. Scoped where you do.
An integration label is not a promise of a ready connector. The proposal states what is available, what will be configured, and what needs new engineering.
| Path | Status | What that means |
|---|---|---|
| GoSense360 business modules | Built-in path | Monitoring and the business modules share the same business records and configuration. Each customer workflow still needs mapping and approval. See the modules |
| SAP | Scoped integration | Objects, APIs or middleware, identity, direction, validation, retries, and acceptance are defined during discovery. |
| Odoo | Scoped integration | No universal ready-made connector is claimed; the required model and workflow are scoped. |
| REST / Webhooks | Scoped interface | Can be designed for an explicit allow-listed event or workflow boundary with secure server-side credentials. |
| CSV exchange | Scoped batch path | Useful when reviewed batch transfer is more appropriate than a live connector. |
Example workflow
Cold-room exception to reviewed ERP action.
This is an example that can be scoped, not a claim that every customer has this workflow active.
- 01
Approved rule
A cold-room condition remains outside a configured threshold for an approved duration.
- 02
Evidence package
The workflow retains the relevant device, location, chronology, and monitored values.
- 03
Draft action
GoSense360 can be scoped to draft a quality hold or ERP workflow for review.
- 04
Human authority
An authorized person reviews and accepts, changes, or rejects the action.
Security & reliability
Integration is a controlled boundary.
Credentials stay server-side, methods are explicit, tenant scope is enforced by the responsible system, and failure must remain visible and recoverable.
Source-of-truth ownership
The integration does not silently move ownership of business records into a dashboard or cache.
Idempotent application
Where a workflow supports replay, stable identities and responsible-system checks reduce duplicate effects.
Visible failure
Unavailability, rejection, and partial progress should surface for retry or investigation rather than be silently discarded.
Discovery output
A production proposal identifies the exact systems, endpoints, objects, credentials boundary, data direction, volume, service owner, test cases, monitoring, rollback, and activation plan. Credentials and sensitive exports should not be submitted through the public enquiry form.
Integration discovery