Build it
What do you want Wachete and Amplitude 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 Amplitude
Triggers and actions 2 triggers · 19 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
Batch upload eventsSends a batch of events to Amplitude in one call. Use this when you have many events to record at once rather than one at a time.
Action
Export event dataExports every event Amplitude recorded in a time window, as a zip archive of event data.
Action
Get cohortReturns one behavioral cohort's details, including its name, size and when it was last recalculated.
Action
Get event segmentationCounts how often an event happened over a date range, optionally split by a property or filtered to a segment of users.
Action
Get funnel analysisRuns a funnel over a series of events and returns how many users reached each step and how many dropped off.
Action
Get retention analysisShows how many users came back and did something again after a starting event, over a date range.
Action
Get user propertiesLooks a user up in Amplitude and returns what Amplitude knows about them, including their Amplitude ID.
Action
Group identifySets properties on a group in Amplitude, such as a company or team, so you can analyse behaviour by group.
Action
Identify userSets properties on a user in Amplitude without recording an event, so later events are attributed with the new details.
Action
List cohortsLists every behavioral cohort in the Amplitude project, with each cohort's name, size and owner.
Action
Send eventRecords a single event in Amplitude for a user, with optional event and user properties.
Action
Upload cohortCreates a cohort in Amplitude from a list of users you supply.
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