Integration

Connect Wachete to Mapulus

When something happens in Wachete, your agent does the next thing in Mapulus. Describe it in plain language and the automation is built, tested on every branch and kept running.

Wachete2 triggersWachete7 actionsMapulus2 triggersMapulus5 actions

Browse all apps

Build it

What do you want Wachete and Mapulus 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 Code

Everything your agent can do with Wachete and Mapulus

Triggers and actions 4 triggers · 12 actions

Trigger
Any new notification
Fires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitor
Delete a Wachete monitor by its ID.
Action
Get monitor
Get information about a specific Wachete monitor by its ID.
Action
Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List folders
List folder contents, optionally under a parent folder.
Action
List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
Action
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.
Trigger
New Location
Triggers when a new location is added in Mapulus.
Trigger
New Map
Triggers when a new map is created in Mapulus.
Action
Create Location
Adds a location pin to a layer on a Mapulus map, from an address or from coordinates.
Action
Delete Location
Removes a location pin from a Mapulus map.
Action
Find Location
Returns Mapulus locations, optionally limited to one map or to the location with a given external ID.
Action
Find Map
Returns the maps in your Mapulus account, so you can pick the one to add locations to.
Action
Update Location
Updates a location pin in Mapulus. Only the fields you supply are changed.

Each app on its own

The other way round: Mapulus to Wachete