Integration
Connect Wachete to redirect.pizza
When something happens in Wachete, your agent does the next thing in redirect.pizza. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Wachete and redirect.pizza 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 redirect.pizza
Triggers and actions 2 triggers · 18 actions
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change 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
Check domain DNSForces redirect.pizza to re-check the DNS records for a domain and returns the domain's updated status.
- Create Redirect
Creates a redirect that sends visitors from one or more source domains to a destination URL.
- Delete Redirect
Deletes a redirect so its source domains no longer forward traffic.
- Get Domain
Returns one domain with its DNS requirements, verification state and SSL status.
- Get Email forward
Returns one email forward, showing which address mail arrives at and where it is delivered.
- Get Redirect
Returns one redirect with its sources, destination, domains and forwarding settings.
- Get Team quota
Returns the connected team, including its plan quota and how much of it is in use.
- List Domains
Returns every domain in the connected team, with each domain's DNS requirements, verification state and SSL status.
- List Email forwards
Returns every email forward in the connected team, showing which address mail arrives at and where it is delivered.
- List Redirects
Returns every redirect in the connected team, with each redirect's sources, destination, domains and forwarding settings.
- Update Redirect
Updates an existing redirect: its sources, destination, redirect type, forwarding and tracking settings, tags or notes.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.