Build it
What do you want Wachete and Ortto 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 Ortto
Triggers and actions 6 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.
Trigger
Fields UpdatedTriggers when the specified field(s) of a record have been updated in your Ortto account.
Trigger
New Activity OccurredTriggers when a new Ortto activity occurs.
Trigger
New Record CreatedTriggers when a new record (contact or organization) has been added to your Ortto account.
Trigger
Tag Added/RemovedTriggers when a tag has beed added to, or removed from, a record.
Action
Add Custom FieldCreate a new custom field on the person or organization schema in Ortto. Endpoint: POST /v1/custom-field/create. Vendor doc: https://help.ortto.com/developer/latest/api-reference/custom-field/
Action
Create RecordCreate a new record (person, organization), or update an existing record in your Ortto account.
Action
Delete RecordArchive, restore, or permanently delete a person or organization record in Ortto. Endpoint: POST /v1/person/delete (and /v1/organization/delete for accounts). Vendor doc: https://help.ortto.com/a-260-archive-restore-and-delete-people-archive-restore-delete
Action
Get RecordFetches one or more people, or one or more accounts, by their Ortto ids, returning whichever fields you ask for.
Action
List ActivitiesRetrieve the activity feed for a given contact in Ortto. Endpoint: POST /v1/person/activities/list (activity log for a contact ID). Vendor doc: https://help.ortto.com/a-773-retrieve-activity-feed-for-a-given-contact
Action
Opt Out From SMSOpt out a person from all SMS communications.
Action
Search or Create RecordsSearch your Ortto data for a record based on the provided field or optionally create one if none is found.
Action
Tag/Untag RecordsAdds or removes tags on a person or an account in Ortto, matching the record by email address or account name.
Action
Unsubscribe a PersonUnsubscribe a person from all emails.
Action
Update Audience SubscriptionSubscribe or unsubscribe a person to/from an Ortto audience. Endpoint: POST /v1/audience/subscribe. Vendor doc: https://help.ortto.com/developer/latest/api-reference/audiences/
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.