Can Lyro search individual property listings through Melo?

Not with these actions. Get Cities, List Searches, and Simulate Webhook cover city availability, saved searches, and webhook testing - none of them return individual adverts or price history. Lyro can tell you what a saved search is looking for, but not enumerate what it currently matches.

What does Simulate Webhook actually send?

It asks the Melo API to post a realistic sample payload - a property match or an event notification, carrying advert details, contact information, and geographic data - to an HTTPS endpoint you specify. Lyro can trigger it on request so you can watch how your handler behaves before live notifications start.

Whose saved searches can Lyro read?

Those of the authenticated Melo account behind the connection. List Searches returns the property searches saved by that user, paginated in the API's Hydra collection format, so what Lyro sees is exactly what that account sees. There is no cross-account view.

How is this different from wiring Melo into Zapier or Make?

Those run a fixed sequence when a webhook fires. Lyro decides what to call while someone is asking - checking a city, pulling the saved search behind their question, then simulating a webhook if the problem turns out to be the endpoint - and hands off to a human agent when the answer sits outside these three actions.

Melo MCP integration

Lists available cities, reads saved property searches and their alert settings, and fires test webhooks at your endpoint.

Connect Melo See all integrations

3actions available

What your agent can do with Melo

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

Get cities
Lyro looks up available cities to verify if properties exist in a customer's desired area. This cuts down response time and prevents mismatched leads.
List searches
Lyro retrieves the customer's saved property searches from Melo to follow up with matching new listings. This keeps the conversation personal and shows the team understands their criteria.

See all 3 actions

How businesses use Melo + Lyro

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

Check which cities are available to search
Lyro pulls the city list with the filters applied, so a question about whether a particular area is covered is settled from the data rather than assumed from the country.
Get CitiesList Searches
Read back what a saved search is looking for
Lyro returns the search with its location filters, budget range, and property types, so a client asking what is being watched on their behalf gets the actual criteria.
List SearchesGet Cities
Confirm whether a search is set to notify
Lyro filters the saved searches by notification status, which answers the common complaint of hearing nothing about a search that was never switched on to alert.
List SearchesGet Cities
Test a webhook endpoint before going live
Lyro triggers a realistic sample payload at your HTTPS endpoint, so the handler is proven against advert and contact data before real property matches start arriving.
Simulate WebhookList Searches

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 Melo actions it has and picks the ones a request needs.

01
Connect Melo
Authorize the Melo 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 Melo 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

Melo · Lyro

Everything else about Melo

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

Not with these actions. Get Cities, List Searches, and Simulate Webhook cover city availability, saved searches, and webhook testing - none of them return individual adverts or price history. Lyro can tell you what a saved search is looking for, but not enumerate what it currently matches.

Every action available in Melo

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

Get cities
Retrieve a list of cities with optional filters.
List searches
Retrieves all property searches saved by the authenticated user from the Melo API.
Simulate webhook
Simulates sending a Melo webhook event to a specified endpoint for testing webhook integrations.