Integration
Connect Wachete to UUID Generator
When something happens in Wachete, your agent does the next thing in UUID Generator. 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 UUID Generator 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 UUID Generator
Triggers and actions 2 triggers · 13 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
Decode UUIDDecode an existing UUID string to extract its version, variant, and (for time-based versions) the embedded timestamp. GET https://www.uuidtools.com/api/decode/{uuid} (endpoint inferred from the site's Decode UUID tool at /decode; confirm exact path when implementing).
Action
Generate timestamp-first UUIDGenerate one or more timestamp-first (ordered) UUIDs, where the current timestamp is embedded at the start so values sort in creation order when stored/indexed. GET https://www.uuidtools.com/api/generate/timestamp-first (endpoint path per the /generate/timestamp-first docs page).
Action
Generate v1 UUIDGenerate one or more (up to 100) time-based version-1 UUIDs. GET https://www.uuidtools.com/api/generate/v1 or /v1/count/{n}.
Action
Generate v3 UUIDGenerate a deterministic version-3 (MD5-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v3/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
Action
Generate v4 UUIDGenerate one or more (up to 100) random version-4 UUIDs. GET https://www.uuidtools.com/api/generate/v4 or /v4/count/{n}.
Action
Generate v5 UUIDGenerate a deterministic version-5 (SHA-1-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v5/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
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