Track web page changes and route them to your on-call tooling
Fluxguard watches web pages and reports what changed. Connect it and Luumen can read your monitored pages, categories, and webhook registrations while you work, then add pages, create categories, register webhook endpoints, or start a crawl as an approved step. Useful for tracking vendor status pages, pricing, and public docs your runbooks depend on. Luumen authenticates with an API key.
13 tools: 6 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Fluxguard run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add fluxguard page, create fluxguard site category, create webhook, delete fluxguard page, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Fluxguard — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.