Wachete is a web monitoring service that allows users to track changes on web pages and receive notifications based on specified criteria.
Wachete is a web monitoring service that allows users to track changes on web pages and receive notifications based on specified criteria. On Nagent, Wachete is exposed as a fully-configurable notifications integration that any agent can call — 11 actions, and API key authentication. No code is required to wire Wachete into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Wachete to automate the kinds of tasks notifications 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 Wachete 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 Wachete, with input parameters and output schema. Drop these into any step of an agent built in Helix.
WACHETE_CREATE_UPDATE_FOLDERCreate a new folder or update an existing folder in Wachete. Folders help organize watchers into hierarchical structures. Omit the id parameter to create a new folder, or provide an id to update an existing one.
Input parameters
Folder ID for updates; omit when creating a new folder.
Name of the folder.
Total number of items in the folder. This field is typically managed by the system and may be ignored in requests.
Parent folder ID. Omit or set to null to create/move folder to root level.
Number of failed tasks in the folder. This field is typically managed by the system and may be ignored in requests.
Number of paused tasks in the folder. This field is typically managed by the system and may be ignored in requests.
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
WACHETE_CREATE_WATCHERCreate or update a Wachete watcher to monitor web page changes. Watchers check pages at specified intervals and send alerts when changes are detected. Use SinglePage mode for monitoring a single page, or Portal mode to crawl and monitor multiple linked pages.
Input parameters
Watcher ID for updates; omit when creating new watcher.
URL to monitor.
Name of the watcher.
XPath selector for the element to watch.
List of alert configurations. Each alert specifies when to notify.
Type of monitoring job: 'SinglePage' for single page or 'Portal' for crawling multiple pages.
URL filters for Portal crawling. Only applicable when jobType='Portal'.
Crawling depth for Portal mode (1, 2, or 3). Only applicable when jobType='Portal'.
Monitoring interval in seconds (e.g., 3600 for hourly, 86400 for daily).
Notification endpoints for alerts. Use Email type for default email, or Webhook with a URL.
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
WACHETE_DELETE_FOLDERPermanently deletes a folder along with all nested subfolders and watchers (monitoring tasks). This is a destructive operation that cannot be undone. Use when you need to remove an entire folder structure. All subfolders and monitoring tasks within the folder will be permanently deleted. Obtain the folder ID from the Get Folder Content action before calling. Example: "Delete the folder with ID 576b3f7e-e126-4e92-9b95-f72a8d187a18"
Input parameters
Unique identifier of the folder to delete. Use the 'id' field returned from Get Folder Content action. Deletes the folder and all nested subfolders and watchers within it.
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
WACHETE_DELETE_WATCHERDeletes a website monitoring watcher (task) by its unique ID. This operation is idempotent - deleting a non-existent or already-deleted watcher will succeed without error. Use when you need to permanently remove a monitoring task. Obtain the watcher ID from List Watchers or Create Watcher actions before calling. Example: "Delete the watcher with ID 974b65b5-6ccb-4996-812c-5a678c2455e8"
Input parameters
Unique identifier of the watcher (task) to delete. Use the 'id' field returned from List Watchers or Create Watcher actions.
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
WACHETE_GET_CRAWLER_PAGESRetrieves all pages monitored by a crawler watcher (portal monitor). Use this to get detailed information about each page being tracked including URLs, last check timestamps, content changes, and error states. Only works with portal-type watchers that monitor multiple pages.
Input parameters
Unique identifier of the watcher (task) to retrieve pages from. This must be a portal-type watcher that monitors multiple pages.
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
WACHETE_GET_DATA_HISTORYRetrieve history for a wachet (monitor). Returns timestamped snapshots of monitored content showing when changes occurred. Supports time range filtering and optional diff with previous value. Use continuationToken for pagination when retrieving large histories.
Input parameters
Wachet (watcher) ID to retrieve history for.
Time interval end (ISO 8601 format). If not provided, retrieves up to present.
Time interval start (ISO 8601 format). If not provided, retrieves from unlimited past.
Number of history items to return. If more items are available, continuationToken is returned for pagination.
If true, returns diff with previous value for each history item. Default is false.
Token for requesting the next result page. Obtained from previous response.
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
WACHETE_GET_FOLDER_CONTENTRetrieves the contents of a Wachete folder, including subfolders and watcher tasks. Use this tool to: - List all subfolders and tasks in the root folder (omit parentId) - List contents of a specific folder (provide parentId) - Navigate the folder hierarchy using the path breadcrumb - Check task statuses and last check data Returns subfolders, tasks with their monitoring details, folder path, and pagination token.
Input parameters
ID of the folder to list contents for. Omit this parameter or pass null to retrieve the root folder contents. Use folder IDs from the 'subfolders' array to navigate into subfolders.
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
WACHETE_GET_WATCHERRetrieve complete watcher (monitor) definition by ID. Use this to get detailed configuration and current status of a specific monitoring task including URL, XPath selector, alerts, notification endpoints, and latest check results.
Input parameters
Unique identifier of the watcher (task) to retrieve. Use the 'id' field returned from List Watchers or Create Watcher actions.
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
WACHETE_LIST_NOTIFICATIONSRetrieves notifications from Wachete watchers. Returns notifications for all watchers or filtered by specific watcher ID and/or time range. Useful for checking recent changes detected by your web page monitors.
Input parameters
ID of a specific watcher to filter notifications. If omitted, notifications for all watchers are returned.
End datetime in ISO 8601 format to filter notifications (inclusive). If omitted, no upper time bound is applied.
Start datetime in ISO 8601 format to filter notifications (inclusive). If omitted, no lower time bound is applied.
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
WACHETE_LIST_WATCHERSList all monitoring watchers (tasks) configured in your Wachete account. Optionally filter by search query. Returns up to 500 watchers with details including name, URL, monitoring settings, and notification configuration.
Input parameters
Optional search query to filter watchers by name or URL. Leave empty to list all watchers.
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
WACHETE_MOVE_ITEMS_TO_FOLDERMove tasks (watchers) and folders to a specified destination folder. Use this to organize your monitoring structure by relocating items within the folder hierarchy. Provide at least one of folderIds or taskIds to move items. Set folderId to null to move items to root level.
Input parameters
List of task (watcher) IDs to move to the destination. Provide this along with folderIds to move multiple items at once.
Destination folder ID where items will be moved. Use null to move items to the root level (no parent folder).
List of folder IDs to move to the destination. Provide this along with taskIds to move multiple items at once.
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 77 agents privately built on Nagent that already use Wachete.
Build on Nagent
Connect Wachete 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 Wachete, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Wachete is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Wachete is connected, you configure its 11 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Wachete 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 Wachete event fires, the agent kicks off automatically.
Every Wachete 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 Wachete ships with 11 pre-built notifications actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Wachete together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Wachete-based workflows tailored to your business.