Sanaf AI
Start free
Server Monitoring

Fluxguard, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Fluxguard account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Server Monitoring
  • Connects with a key
  • 23 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Fluxguard is

Fluxguard is an AI-powered website change detection and monitoring tool that helps businesses track, analyze, and respond to critical changes in web-based data.

You paste in a key from your own Fluxguard account. It is kept encrypted, and you can withdraw it from inside Fluxguard whenever you like.

How a run works

One message in, the work done in Fluxguard.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Fluxguard. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Fluxguard account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

23 tools it already has

What it can do in Fluxguard

These are the ready-made tools your AI employee already has in Fluxguard. It is not limited to them, but it never has to be taught these.

  • Acknowledge Fluxguard AlertTool to acknowledge an alert, marking it as reviewed. Since Fluxguard's public API does not currently expose an acknowledge endpoint, we perform a real API call to the official sam
  • Add FluxGuard PageTool to add a new page for monitoring. Use when you need to start monitoring a URL by adding it to FluxGuard.
  • Create FluxGuard Site CategoryTool to create a new site category in FluxGuard. Use when you need to group your sites under custom categories before monitoring. Invoke after authenticating your account.
  • Create WebhookTool to create a new webhook for receiving notifications about monitored pages. Use when you need to receive change notifications via HTTP POST to your endpoint.
  • Delete Fluxguard PageTool to delete a monitored page. Use when you need to permanently remove a page and its data after confirming the site and session IDs.
  • Delete Fluxguard SiteTool to delete a monitored site. Use when you need to permanently remove a site and all its data.
  • Delete WebhookTool to delete a webhook. Use when you need to remove a webhook by its ID.
  • Fluxguard Webhook NotificationTool to send change data to your webhook endpoint. Use when a modification is detected.
  • Get Alert DetailsTool to retrieve details of a specific alert. Use after obtaining the alert ID. Returns full alert information.
  • Get ChangesTool to retrieve a list of all detected changes across monitored sites. Since there is no public "list changes" endpoint, this action uses the sample webhook endpoint as a surrogat
  • Get FluxGuard Account DataTool to retrieve general account information for your FluxGuard organization. Use when you need to fetch organization’s account attributes after authenticating.
  • Get FluxGuard AlertsTool to retrieve all alerts generated by site changes. Since Fluxguard's public API does not expose an alerts listing endpoint, we leverage the sample webhook payload to provide a
  • Get Fluxguard ChangeTool to retrieve details of a change by its ID. Use after you have a valid change ID to fetch its details.
  • Get FluxGuard Site CategoriesTool to retrieve all site categories. Use when you need to list every category defined in your organization.
  • Get FluxGuard Site DetailsTool to retrieve details of a specific monitored site by its ID. Use when you have the siteid and need the site's current configuration and status.
  • Get FluxGuard SitesTool to retrieve a list of all monitored sites. Use when you need to enumerate all sites after authenticating.
  • Get FluxGuard User DetailsTool to retrieve details that represent the current FluxGuard account as a user-like object. FluxGuard does not expose a public users endpoint; we map /account attributes to a user
  • Get FluxGuard UsersTool to retrieve all users in the organization. Since FluxGuard's public API does not expose a users listing endpoint, we leverage a documented endpoint and return an empty list wh
  • Get FluxGuard WebhooksTool to retrieve all configured webhooks. Use when you need a list of webhook configurations.
  • Get Sample Webhook PayloadTool to retrieve a sample webhook payload. Use when you need to inspect the structure of webhook notifications.
  • Get Site SnapshotsTool to retrieve a list of all site snapshots. Use when you need to enumerate available snapshots for your account.
  • Get SnapshotTool to retrieve details of a specific snapshot by its ID. Since Fluxguard does not expose a public snapshot lookup endpoint, this action searches the sample webhook payload for a
  • Get Webhook DetailsTool to retrieve details of a specific webhook by its ID. Use when you need to fetch up-to-date configuration of a webhook.
Access, and who is in charge of it

You stay the boss of your Fluxguard account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Fluxguard account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Fluxguard is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Fluxguard and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Fluxguard

Can an AI employee really work inside Fluxguard?
Yes. It signs in to your own Fluxguard account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Fluxguard?
No. Nothing moves and nothing is replaced. Your records stay in Fluxguard, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Fluxguard account?
You paste in a key from your own Fluxguard account. It is kept encrypted, and you can withdraw it from inside Fluxguard whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Fluxguard?
It has 23 ready-made tools in Fluxguard today, among them Acknowledge Fluxguard Alert, Add FluxGuard Page and Create FluxGuard Site Category. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Fluxguard and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Fluxguard and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Fluxguard?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Fluxguard is written down with what it did and when.