# Fluxguard AI integration on Definable

> 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.

## What this connects

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.

Vendor: https://fluxguard.com/

## Tools available

**13** tools available. First 12:

- `FLUXGUARD_ADD_PAGE` — Add FluxGuard Page — Tool to add a new page for monitoring in FluxGuard. This action can: 1. Create a new site with a page (when siteId/sessionId are not provided) 2. Add a page to an existing site (when siteId/sessionId are provided) When creating a new site, you can optionally assign it to categories and provide a nickname. Use this when you need to start monitoring a URL for changes.
- `FLUXGUARD_CREATE_SITE_CATEGORY` — Create FluxGuard Site Category — Creates a new site category in FluxGuard for organizing monitored websites. Site categories help you group and manage your monitored sites logically (e.g., by environment like 'Production' or 'Staging', by purpose like 'Marketing' or 'E-commerce', or by client/team). Use this action to create categories before adding sites, making it easier to filter and organize your monitoring dashboard. The returned category ID can be used when adding sites to assign them to this category.
- `FLUXGUARD_CREATE_WEBHOOK` — Create Webhook — Creates a webhook endpoint registration in FluxGuard to receive real-time notifications when changes are detected on monitored pages. When changes occur, FluxGuard will POST JSON data to your specified URL containing change details, diff information, and file references. Use this when you need to integrate FluxGuard change detection into your own systems, automation workflows, or alerting infrastructure. Note: Only one webhook can be active per account. Creating a new webhook will replace any existing webhook configuration.
- `FLUXGUARD_DELETE_PAGE` — Delete Fluxguard Page — Permanently deletes a monitored page from FluxGuard along with all its captured snapshots and version history. This is a destructive operation that cannot be undone. Use this when you need to remove a page that is no longer needed for monitoring. The operation is idempotent - deleting an already-deleted page will succeed without error. To obtain the required IDs (site_id, session_id, page_id), first use FLUXGUARD_ADD_PAGE to create a page or FLUXGUARD_GET_SITES to list existing sites and their pages.
- `FLUXGUARD_DELETE_SITE` — Delete Fluxguard Site — Permanently deletes a monitored site and all associated data including sessions, pages, and captured versions. This operation is idempotent - deleting a non-existent site returns success. Use when you need to remove a site from FluxGuard monitoring.
- `FLUXGUARD_DELETE_WEBHOOK` — Delete Webhook — Permanently removes a webhook from your FluxGuard account by its ID. After deletion, the webhook will no longer receive notifications about monitored page changes. This operation is idempotent - deleting a non-existent webhook will succeed without error. Use this tool when you need to remove a webhook configuration that is no longer needed.
- `FLUXGUARD_GET_ALL_CATEGORIES` — Get All FluxGuard Categories — Retrieves all categories defined in your FluxGuard account. Use this tool when you need to: - List all available categories for organizing sites or pages - Get category IDs for use in other operations - Check what categories exist before creating new ones This is a read-only operation that returns both site and page categories. No parameters are required - simply call this action to get all categories.
- `FLUXGUARD_GET_PAGE_DATA` — Get FluxGuard Page Data — Tool to retrieve comprehensive data for a monitored page in FluxGuard. This action fetches detailed information about a specific page including its URL, monitoring status, capture history, and metadata. Use this when you need to verify a page exists, check its monitoring status, or retrieve page configuration details. The page must be identified by its site_id, session_id, and page_id, which are typically obtained from FLUXGUARD_ADD_PAGE when creating a page or from FLUXGUARD_GET_SITES when listing existing sites and their pages.
- `FLUXGUARD_GET_SAMPLE_WEBHOOK` — Get Sample Webhook Payload — Tool to retrieve a sample webhook payload. Use when you need to inspect the structure of webhook notifications.
- `FLUXGUARD_GET_USER` — Get Current FluxGuard Account — Retrieves the authenticated FluxGuard account's information as a user profile. Returns details about the current organization's account including ID, status, creation date, and last update timestamp. This provides account information in a user-friendly format for the authenticated API key's organization.
- `FLUXGUARD_GET_WEBHOOKS` — Get FluxGuard Webhooks — Retrieves all configured webhooks for the FluxGuard account. Use this action to list all webhook endpoints that are configured to receive FluxGuard change notifications. Each webhook includes its URL, secret for signature verification, API version, and associated site categories. No parameters required - returns all webhooks for the authenticated account.
- `FLUXGUARD_INITIATE_CRAWL` — Initiate FluxGuard Crawl — Tool to initiate a crawl for a session identified by siteId and sessionId. Use when you need to start monitoring a site for changes after adding pages with FLUXGUARD_ADD_PAGE.

## Auth

Auth schemes: `API_KEY`.

## How agents use Fluxguard

Inside a Definable workflow, Fluxguard is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Fluxguard** — the Researcher (GPT-5.5) pulls context from Fluxguard (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Fluxguard** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Fluxguard (create record, post message, draft email).
- **Designer / Engineer → Distributor → Fluxguard** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Fluxguard (attach file, open PR comment, post status).

The Verifier checks every Fluxguard call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- server monitoring — https://definable.ai/apps/category/server-monitoring/
- analytics — https://definable.ai/apps/category/analytics/

## Related

- HTML page: https://definable.ai/apps/fluxguard/
- Same category (server monitoring): https://definable.ai/apps/category/server-monitoring/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt