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.
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.
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.
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.
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.
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.
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.
Simulate Fluxguard webhook notification by sending change detection data to your webhook endpoint. Use this tool to test your webhook receiver implementation by sending it a properly formatted Fluxguard webhook payload with optional HMAC signature authentication. This helps verify your endpoint can receive and process Fluxguard change notifications correctly. Note: This does NOT retrieve data from Fluxguard or trigger actual monitoring - it only sends test notifications to your webhook URL.
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.
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.
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.
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.
Tool to retrieve a sample webhook payload. Use when you need to inspect the structure of webhook notifications.
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.
The Fluxguard integration connects your Dench AI CRM directly to Fluxguard, so agents can read and act on your Fluxguard data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
13 actions are available for agents to invoke on your behalf. Every call runs through Fluxguard's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Fluxguard and click Connect — you'll authorize access through Fluxguard's own sign-in flow. No API keys or code required.
Ask an agent to use Fluxguard in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Fluxguard integration connects your AI CRM to Fluxguard, so AI agents can work with your Fluxguard data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Fluxguard integration currently exposes 13 actions, including Add FluxGuard Page, Create FluxGuard Site Category, Create Webhook, Delete Fluxguard Page, Delete Fluxguard Site, and Delete Webhook. Agents invoke them on your behalf from chat or from automations.
No. You connect Fluxguard from your Dench workspace using Fluxguard's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Fluxguard's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Fluxguard connection from your workspace settings at any time.