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.
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. On Nagent, Fluxguard is exposed as a fully-configurable server monitoring integration that any agent can call — 13 actions, and API key authentication. No code is required to wire Fluxguard into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Fluxguard to automate the kinds of tasks server monitoring teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Fluxguard into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Fluxguard, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FLUXGUARD_ADD_PAGETool 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.
Input parameters
URL of the page to monitor. This is the web page that FluxGuard will track for changes.
ID of an existing site to add this page to. Must be provided together with sessionId. If omitted, a new site will be created automatically.
ID of the session containing the existing site. Must be provided together with siteId. If omitted, a new site and session will be created automatically.
List of category IDs to assign to the newly created site. Only applies when creating a new site (when siteId/sessionId are not provided). Use FLUXGUARD_GET_ALL_CATEGORIES to retrieve available category IDs.
Single category ID to assign to the newly created site. Only applies when creating a new site. Cannot be used with 'categories' parameter.
Name of a single category to assign to the newly created site. Only applies when creating a new site. The category must already exist in your FluxGuard account.
Human-readable nickname for the newly created site. Only applies when creating a new site (when siteId/sessionId are not provided).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_CREATE_SITE_CATEGORYCreates 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.
Input parameters
The name for the new site category. Use descriptive names to organize your monitored sites (e.g., 'Production', 'Development', 'Client Sites').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_CREATE_WEBHOOKCreates 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.
Input parameters
The HTTPS URL endpoint where FluxGuard will POST JSON notifications when changes are detected on monitored pages. Must be publicly accessible.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_DELETE_PAGEPermanently 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.
Input parameters
Unique identifier of the specific page to permanently delete. Obtain this from the response of FLUXGUARD_ADD_PAGE action.
Unique identifier of the site containing the page to delete. Obtain this from the response of FLUXGUARD_ADD_PAGE or FLUXGUARD_GET_SITES actions.
Unique identifier of the monitoring session under the site. Obtain this from the response of FLUXGUARD_ADD_PAGE action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_DELETE_SITEPermanently 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.
Input parameters
Unique identifier of the site to delete. Accepts both short alphanumeric IDs (e.g., '53z1wfkw098tj') and UUID format (e.g., '331dd37e-f2af-4323-9424-0e0cc4dee8aa')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_DELETE_WEBHOOKPermanently 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.
Input parameters
The unique identifier of the webhook to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_GET_ALL_CATEGORIESRetrieves 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_GET_PAGE_DATATool 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.
Input parameters
Unique identifier of the specific page to retrieve data for. Obtain this from FLUXGUARD_ADD_PAGE action.
Unique identifier of the site containing the page. Obtain this from FLUXGUARD_ADD_PAGE or FLUXGUARD_GET_SITES actions.
Unique identifier of the monitoring session under the site. Obtain this from FLUXGUARD_ADD_PAGE action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_GET_SAMPLE_WEBHOOKTool to retrieve a sample webhook payload. Use when you need to inspect the structure of webhook notifications.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_GET_USERRetrieves 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.
Input parameters
Identifier for the user to retrieve. Use 'current' or 'me' to get the authenticated account's information.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_GET_WEBHOOKSRetrieves 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_INITIATE_CRAWLTool 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.
Input parameters
Unique identifier of the site to crawl. Can be alphanumeric (e.g., '559kz95p1x7de') or UUID format. Use FLUXGUARD_ADD_PAGE to create a site and obtain a site ID.
Unique identifier of the session within the site. Obtained from FLUXGUARD_ADD_PAGE when adding a page to a site.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUXGUARD_WEBHOOK_NOTIFICATIONSimulate 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.
Input parameters
Optional webhook signing secret to generate HMAC-SHA256 signature in fluxguard-signature header for authentication
Complete webhook payload with change detection data to send
The webhook endpoint URL where the notification will be sent (e.g., https://your-server.com/webhooks/fluxguard)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 94 agents privately built on Nagent that already use Fluxguard.
Build on Nagent
Connect Fluxguard to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Fluxguard, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Fluxguard is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Fluxguard is connected, you configure its 13 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Fluxguard steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Fluxguard event fires, the agent kicks off automatically.
Every Fluxguard action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Fluxguard ships with 13 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Fluxguard together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Fluxguard-based workflows tailored to your business.