Can FluxGuard notify more than one endpoint about a change?

No. Only one webhook can be active per account, and Create Webhook replaces the existing configuration rather than adding a second. Have Lyro check Get FluxGuard Webhooks first if another system is already receiving change notifications.

How does Lyro get the IDs for a page it did not create?

They have to be supplied. Page-level actions need site_id, session_id, and page_id, and those come back from Add FluxGuard Page at creation time. This toolkit has no list-sites action, so for pages set up earlier the IDs come from your FluxGuard dashboard.

Does the webhook test action send real change data?

No. Fluxguard Webhook Notification sends a correctly formatted sample payload, with optional HMAC signature, to your endpoint so you can verify the receiver handles it. It reads nothing from FluxGuard and triggers no monitoring.

What is lost when Lyro deletes a monitored page?

The page, its captured snapshots, and its full version history, permanently. Deleting a site goes further and removes every session, page, and captured version beneath it. Both operations are idempotent, so repeating one on something already deleted still returns success.

Fluxguard MCP integration

Starts monitoring a URL, groups sites into categories, triggers crawls, and wires change notifications into your own systems.

Connect Fluxguard See all integrations

13actions available

Three actions you can hand over today

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

Get fluxguard page data
Lyro retrieves comprehensive monitoring data for a page including uptime, changes, and performance. Alerts you to drift or downtime in real time.
Add fluxguard page
Lyro registers a new page for monitoring in FluxGuard. Starts tracking that URL for changes and availability immediately.
Get current fluxguard account
Lyro fetches your account profile and monitoring settings. Shows you what you're tracking and your current usage at a glance.

See all 13 actions

How businesses use Fluxguard + Lyro

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

Put a URL under monitoring from the conversation
Lyro adds the page, creating a new site when no site or session ID is given and attaching it to an existing one when they are, then starts the crawl for that session.
Add FluxGuard PageCreate FluxGuard Site CategoryInitiate FluxGuard Crawl
Check what a monitored page is doing
Lyro retrieves a page's URL, monitoring status, capture history, and configuration, lists the site and page categories defined on the account, and confirms which account the key belongs to.
Get FluxGuard Page DataGet All FluxGuard CategoriesGet Current FluxGuard Account
Send change detections into your own systems
Lyro registers the endpoint FluxGuard POSTs change details, diffs, and file references to, lists the webhooks already configured with their signing secrets, and fires a sample payload at a new receiver.
Create WebhookGet FluxGuard WebhooksGet Sample Webhook Payload
Retire monitoring that is no longer needed
Lyro deletes a page with its snapshots and version history, removes a whole site along with every session under it, or clears a webhook that has been replaced.
Delete FluxGuard PageDelete FluxGuard SiteDelete Webhook

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

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

Fluxguard · Lyro

Everything else about Fluxguard

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

No. Only one webhook can be active per account, and Create Webhook replaces the existing configuration rather than adding a second. Have Lyro check Get FluxGuard Webhooks first if another system is already receiving change notifications.

Every action available in Fluxguard

All 13 actions your agent can call on Fluxguard, straight from the live MCP connection.

Add fluxguard page
Add a new page for monitoring in FluxGuard.
Create fluxguard site category
Creates a new site category in FluxGuard for organizing monitored websites.
Create webhook
Creates a webhook endpoint registration in FluxGuard to receive real-time notifications when changes are detected on monitored pages.
Delete fluxguard page
Permanently deletes a monitored page from FluxGuard along with all its captured snapshots and version history.
Delete fluxguard site
Permanently deletes a monitored site and all associated data including sessions, pages, and captured versions.
Delete webhook
Permanently removes a webhook from your FluxGuard account by its ID.
Get all fluxguard categories
Retrieves all categories defined in your FluxGuard account.
Get fluxguard page data
Retrieve comprehensive data for a monitored page in FluxGuard.
Get sample webhook payload
Retrieve a sample webhook payload.
Get current fluxguard account
Retrieves the authenticated FluxGuard account's information as a user profile.
Get fluxguard webhooks
Retrieves all configured webhooks for the FluxGuard account.
Initiate fluxguard crawl
Initiate a crawl for a session identified by siteId and sessionId.
Fluxguard webhook notification
Simulate Fluxguard webhook notification by sending change detection data to your webhook endpoint.