Wachete
Developer ToolsCreate and manage Wachete monitors that watch web pages for changes and raise alerts when they happen. Agents react to a competitor, policy, or price change the moment it is detected.
What This Integration Enables
Wachete and page monitoring in general get lumped together, but Wachete is built around a different object. An XPath points the monitor at a fragment, and what Wachete stores for that fragment on every check is a value: the number in the price cell, the text in the status field, the date on the certificate. Get Monitor History returns that series with the time each value was checked and the time it last changed, optionally with a Google diff breakdown of what was added and removed between consecutive readings. So the output of a Wachete monitor is not only "something changed," it is a column of data a workflow can write into a sheet, compare against a threshold, or chart.
The second thing Wachete assumes is scale. Monitors live in a folder tree, Search Monitors accepts qualifiers such as type:dynamic across as many as 500 results per call, Move To Folder relocates a batch of monitors and folders in one operation, and Get Account Overview walks the tree and counts every monitor plus the failing and paused totals each folder reports. That is a design for someone running hundreds of watches across suppliers, jurisdictions and internal endpoints, not someone watching three pages. FlowRunner agents provision, file and reorganise that estate from inside a flow, then hand the reading of any individual change to the person who owns the consequence.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Regulatory and tender page watch with an owner per folder
A public sector team watches tender portals and regulatory guidance pages across several jurisdictions. The agent creates one folder per jurisdiction with Create Folder, provisions a monitor per page with the XPath pointed at the listing body, and files each with Move To Folder. When a page changes, On Monitor Alert delivers the new and previous values, the agent pulls Get Notification Content for the marked up report, and posts it to the jurisdiction's channel in Slack. New tenders get an issue in Jira with the source URL and the extracted listing text attached.
Certificate and status page escalation before something breaks
Monitors watch certificate expiry dates and third party status pages, with the XPath pointed at the expiry field or the status string. Because Wachete records the extracted value rather than a diff, the agent can compare the current value against a date threshold instead of parsing an alert. When an expiry falls inside the warning window, or a status page flips from operational, the agent raises the incident in PagerDuty and posts context into the ops channel. The Portal monitor type extends this to a whole documentation site: Get Crawled Pages lists the sub pages discovered from the root with each page's own latest value.
Rebuilding a monitor estate after a reorganisation
A supplier list is reshuffled and forty monitors need to move from one owner's folder to another. The agent runs Search Monitors for the supplier's URLs, creates the target folder, and calls Move To Folder once with the whole batch. It then runs Get Account Overview and posts the resulting counts, including failing and paused monitors per folder, to the ops lead in Notion. Nobody clicks through forty screens, and the failing count surfaces watches that quietly stopped working while everyone assumed they were covered.
Human-in-Loop Highlight
The gate on this connector sits in an unusual place: switching a monitor to realtime alerting. Wachete has no webhook subscription API, so enabling the On Monitor Alert trigger works by adding a webhook notification endpoint to the monitor's own definition. That is a write, not a subscription. And a Wachete monitor with no explicit notification endpoints notifies every account email address by default, which means the act of adding the FlowRunner endpoint can silently end the email alerts a compliance or ops team has been relying on for months without anyone noticing until an alert does not arrive.
So when an agent is asked to convert a folder of monitors from polling to realtime, it stops before the first write and asks the monitor owner in their channel: "Switching these 14 monitors in the EU Regulatory folder to realtime alerts will add a webhook endpoint to each definition. Any of these currently relying on the default email fan out will stop emailing your team. Confirm, and name the addresses to add explicitly so the emails keep working." The agent then applies the change with Update Monitor, which reads the current definition first and only alters supplied fields, so nothing else on the monitor is cleared. The same rule governs Delete Folder, which removes every subfolder and every monitor inside it and is recoverable only from the Wachete profile for a limited window, never through the API, and Invalidate API Tokens, which immediately cuts off any other integration still holding a token. Those are automation exceptions by design, routed to a person rather than absorbed by the agent.
Agent Capabilities
16 actionsMonitors
6- Create Monitor Creates a new monitor (a "wachet") that repeatedly fetches a URL and alerts when the watched content changes or the page errors. Monitor a whole page or just the fragment selected by an XPath, optionally rendering JavaScript, sending custom headers, or crawling sub pages as a Portal monitor.
- Update Monitor Updates an existing monitor. The current definition is read first and only supplied fields are changed, so settings left empty keep their existing values rather than being cleared. This is the safe way for an agent to adjust one setting on a monitor it did not create.
- Get Monitor Retrieves the full definition of a single monitor, including URL, XPath, check interval, alert conditions, notification endpoints and the latest extracted value with its last checked and last changed timestamps.
- Delete Monitor Permanently deletes a monitor and stops all checks and notifications for it. Deleted monitors can be recovered for a limited period from the Wachete profile's Account tab, but not through the API.
- Search Monitors Searches every monitor on the account and returns matching definitions, up to 500 per call. Accepts plain text matched against monitor names and URLs as well as Wachete's search qualifiers such as type:dynamic. Leave the query empty to list monitors without filtering.
- Get Crawled Pages Lists the sub pages a Portal monitor discovered from its root URL, each with its own URL and latest extracted value. Single Page monitors return an empty list.
Monitoring Results
3- Get Monitor History Retrieves the recorded value history of a monitor: every check with its extracted value, the time it was checked, the time the value last changed, and any error. Optionally returns a Google diff breakdown of additions and removals between consecutive values instead of plain values.
- List Notifications Lists alerts already triggered, newest first, across the whole account or for one monitor. Each notification carries the monitor name and URL, the current and previous values, any error text, and when it fired.
- Get Notification Content Retrieves the rendered HTML body of a single notification, the same change report Wachete emails, with removed content marked in red and added content in green. Use the notification ID from List Notifications or from the On Monitor Alert trigger.
Folders
5- List Folder Content Lists the direct content of one folder: its subfolders, the monitors filed in it, and the folder path leading to it. Each subfolder reports how many monitors it holds and how many of those are failing or paused.
- Create Folder Creates a new folder for organising monitors, optionally nested inside an existing folder. Returns the created folder with its generated ID for use when creating or moving monitors.
- Rename Folder Renames an existing folder and optionally moves it under a different parent. The monitors filed in the folder are unaffected.
- Delete Folder Permanently deletes a folder together with every subfolder and every monitor inside it, stopping all their checks and notifications. Recovery is possible for a limited period from the Wachete profile only, not through the API.
- Move To Folder Moves any number of monitors and folders into a target folder in a single call, so a batch can be reorganised without editing each definition. Leave the target empty to move items to the root.
Account
2- Get Account Overview Summarises account usage by walking the folder tree and counting every monitor and folder found, plus the failing and paused counts each folder reports. Useful for checking headroom against a subscription's monitor allowance. Wachete exposes no plan or quota endpoint, so the totals are counted from folder listings.
- Invalidate API Tokens Invalidates every bearer token previously issued for the account, immediately cutting off any integration still holding one. Use after a key leak. Existing monitors and their data are untouched.
Triggers
2 triggersEvent Triggers
2- On Monitor Alert Fires the moment a chosen monitor raises an alert, delivered by a Wachete webhook with the new and previous values, which is faster than the polling alternative. Because Wachete has no webhook subscription API, enabling this adds a webhook notification endpoint to the monitor's own definition and removes it again when the trigger is deleted. A monitor with no explicit endpoints notifies every account email by default, so add at least one email to the monitor to keep those emails flowing.
- On New Notification Watches Wachete's notification feed and fires for every alert raised since the previous cycle, either across the whole account or for one monitor. It never modifies a monitor's definition, which makes it the safer choice when monitors already rely on their existing notification endpoints. The first cycle records current notifications only, so an established account does not replay its backlog.
Frequently Asked Questions
What can FlowRunner do with Wachete?
FlowRunner agents can run Create Monitor, Update Monitor, and Get Monitor in Wachete, plus 13 more actions.
Does connecting Wachete to FlowRunner require OAuth?
No. Wachete connects to FlowRunner with an API key, no OAuth flow required.
Can Wachete trigger a FlowRunner workflow automatically?
Yes. Wachete supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with Wachete
$100 in credits. No card required. Connect in minutes.