What does the Hystruct integration let Lyro do?

One thing: list every webhook configured on the connected Hystruct account, including where each one delivers its scrape results. It does not create scrape jobs or change a webhook's configuration.

Can Lyro create or edit a Hystruct webhook?

No - the connected action only lists existing webhooks. Creating a schema, starting a scrape, or changing a webhook's destination still happens in Hystruct directly.

Does Lyro see the actual scraped data, or just the webhook list?

Just the webhook list - which endpoints are configured and what they're tied to. The structured data Hystruct extracts is delivered to those endpoints directly, not through this connection.

How is this different from checking webhooks through Zapier or Make?

Those would need their own separate connection to Hystruct's API. Lyro lists the webhooks directly inside the conversation, so confirming delivery setup doesn't require opening another tool.

Hystruct MCP integration

Lists every webhook on a connected Hystruct account, so a team can confirm where scrape results are routed.

Connect Hystruct See all integrations

1actions available

What your agent can do with Hystruct

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

List all webhooks
Lyro retrieves all webhooks configured in your Hystruct account. You verify which integrations are active and troubleshoot delivery issues quickly.

See all 1 actions

How businesses use Hystruct + Lyro

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

Confirm where scrape results are going
When a team needs to know which endpoint a Hystruct scrape is delivering to, Lyro lists the account's webhooks and confirms the delivery target.
List All WebhooksConfirm Delivery Target
Audit webhook setup without opening the dashboard
Lyro reads back every webhook configured on the account, so a setup review happens inside the conversation instead of the Hystruct dashboard.
List All WebhooksConfirm Delivery Target
Troubleshoot a scrape result that didn't arrive
If a scrape result seems to be missing, Lyro lists the account's webhooks so the team can confirm the destination is still correctly configured.
List All WebhooksConfirm Delivery Target
Verify setup before scaling to a new schema
Before adding a new scrape schema, Lyro lists the existing webhooks so the team can confirm results will land where expected.
List All WebhooksConfirm Delivery Target

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

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

Hystruct · Lyro

Everything else about Hystruct

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

One thing: list every webhook configured on the connected Hystruct account, including where each one delivers its scrape results. It does not create scrape jobs or change a webhook's configuration.