Build it
What do you want Wachete and Updown.io to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Wachete and Updown.io
Triggers and actions 2 triggers · 17 actions
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
Action
Create CheckCreates a new uptime check in updown.io for a URL you want monitored, and returns the created check including its token.
Action
Create RecipientAdds a new alert recipient (email, SMS, webhook, Slack-compatible or Microsoft Teams) to your updown.io account and returns the created recipient.
Action
Delete CheckDeletes an uptime check from updown.io by its token.
Action
Delete RecipientRemoves an alert recipient from your updown.io account by its id.
Action
Get CheckReturns a single updown.io uptime check by its token, including its current status, uptime and settings.
Action
Get Check MetricsReturns performance metrics for an updown.io check over a period — uptime, apdex, request counts and average timings, optionally grouped by time or monitoring location.
Action
List ChecksReturns every uptime check on your updown.io account with its current status and settings.
Action
List DowntimesReturns the recorded outages for an updown.io check, newest first, with the reason, start and end times and duration of each.
Action
List RecipientsReturns every alert recipient on your updown.io account — email addresses, phone numbers, webhooks and chat integrations.
Action
Update CheckUpdates the settings of an existing updown.io uptime check — its URL, name, interval, threshold, alert muting and more. Anything left blank keeps its current value.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews