What is the external ID Lyro searches on?

It is the identifier your other systems use for the same place - typically the record ID from a CRM or database that was stored against the Mapulus location. Find Location by External ID matches on that value and returns every location carrying it, which is what makes a customer record and a map point line up without a manual search.

Can Lyro create or move a location on one of our maps?

No. All three actions - Find Location by External ID, Get Map Details, and List Maps - are reads. Connecting Mapulus lets Lyro answer questions about your maps; it cannot add, edit, or delete a location, so no conversation can change your map data.

Which maps can Lyro see?

Only the maps the authenticated account can access. List Maps returns that account's maps with their IDs, titles, and timestamps, so scoping Lyro's reach is a matter of which Mapulus account sits behind the connection rather than a separate permission list.

What happens if nothing is mapped against the ID?

Find Location by External ID returns an empty list rather than an error or a nearest guess, so Lyro reports that no location matches instead of inventing one. If the answer matters to the customer, it hands the conversation to a human agent with the full history attached.

Mapulus MCP integration

Finds a location by its external ID, returns full map metadata, and lists every map the connected account can reach.

Connect Mapulus See all integrations

3actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

List maps
Lyro retrieves all maps accessible to your account with details about each. You quickly locate a map or check which locations are mapped.
Get map details
Lyro fetches detailed information about a specific map including points and layers. You verify location data or troubleshoot map display issues.
Find location by external ID
Lyro finds locations in Mapulus using their external system identifier. You sync location data across systems or look up specific stores or branches.

See all 3 actions

How businesses use Mapulus + Lyro

Each card is one request a support team gets, and the Mapulus actions Lyro runs to close it.

Find a location by the ID your CRM already uses
Lyro looks the place up by the external identifier stored against it, so a record in your CRM or database resolves to its mapped location without anyone hunting for it by name.
Find Location by External IDList Maps
Tell someone which maps they can actually open
Lyro lists the maps available to the connected account, filtered by name or tag, so a request for the right territory map ends with a specific map instead of a forwarded question.
List MapsGet Map Details
Confirm a location is actually on the map
Before anyone promises a visit or a delivery, Lyro checks whether a location exists for that external ID and says plainly when nothing matches.
Find Location by External IDGet Map Details
Bridge a customer record to its point on the map
In one exchange Lyro resolves the external ID to a location and pulls the metadata of the map holding it, joining the record and the geography without an export in between.
Find Location by External IDGet Map DetailsList Maps

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Mapulus actions it has and picks the ones a request needs.

01
Connect Mapulus
Authorize the Mapulus account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Mapulus actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Mapulus · Lyro

Everything else about Mapulus

Setup, permissions, and the limits of what Lyro can do inside Mapulus.

It is the identifier your other systems use for the same place - typically the record ID from a CRM or database that was stored against the Mapulus location. Find Location by External ID matches on that value and returns every location carrying it, which is what makes a customer record and a map point line up without a manual search.

Every action available in Mapulus

All 3 actions your agent can call on Mapulus, straight from the live MCP connection.

Find location by external ID
Find locations by their external identifier.
Get map details
Retrieve detailed information about a map.
List maps
Retrieves a paginated list of all maps accessible to the authenticated user.