Integrations
Sensemore LAKE pushes events to your systems through webhooks, accepts reads and writes through a scoped API key, and answers AI assistants over MCP.
A monitoring platform that cannot talk to the rest of the plant becomes one more screen nobody opens. Sensemore LAKE connects three ways: it pushes what happens to your systems, your systems read from and write into it, and an AI assistant can reach it directly.
Outbound: LAKE Tells Your Systems What Happened
An outbound integration posts to a URL you own the moment something happens. You choose which events are worth a call:
- a telemetry value, or an alarm
- a work order raised, or its status changed
- an asset created, or updated
- an inventory change
- a production order raised, or its status changed
- a report generated
The request method and up to ten custom headers are yours to set, which is usually what a corporate endpoint asks for before it will accept anything.
Inbound: Your Systems Read and Write
An inbound integration works through an API key with scopes, so a connection is granted exactly what it needs and nothing more. The scopes cover assets, time series, work orders, inventory and production orders, each readable, writable, or both.
That separation matters when a connection is built by somebody outside the maintenance team. A key that can read time series and nothing else cannot close a work order by accident.
For Assistants: MCP
The third route is newer and is aimed at the AI assistants a team already uses rather than at systems. Over the MCP server an assistant reads trends, spectra and bearing scores directly, and can raise a work order once a person approves it. The tools that change anything are a small, explicit minority; everything else only reads.
Types and Direction
Every integration declares what it is and which way the data moves. The type is an ERP connection, an IoT gateway, or something custom. The direction is inbound, outbound or both. A sandbox flag lets a connection be exercised before it touches anything that matters.
When One Breaks, You Can See It
Each integration records when it last succeeded, when it last failed and what the error said. This is worth more than it sounds: a silently dead integration is the expensive kind, because the data stops arriving long before anybody notices it stopped.
Where to Find It
Integrations sit under Connectivity in LAKE. The developer page covers the API itself, and the MCP server covers connecting an assistant.