Integration
Connect Wachete to Intelliprint
When something happens in Wachete, your agent does the next thing in Intelliprint. 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 Intelliprint 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 Intelliprint
Triggers and actions 2 triggers · 22 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
Add backgroundCreate a background/letterhead used for print jobs. POST /backgrounds
Action
Add mailing listCreate a mailing list. POST /mailing_lists
Action
Add recipientCreate a recipient in a mailing list. POST /mailing_lists/{mailing_list}/recipients
Action
Delete mailing listDelete a mailing list. DELETE /mailing_lists/{id}
Action
Delete print jobDelete or cancel a print job. DELETE /prints/{id}
Action
Delete recipientDelete a mailing list recipient. DELETE /mailing_lists/{mailing_list}/recipients/{id}
Action
Get mailing listRetrieve a mailing list by id. GET /mailing_lists/{id}
Action
Get print jobRetrieve a single print job by id. GET /prints/{id}
Action
Get recipientRetrieve a mailing list recipient by id. GET /mailing_lists/{mailing_list}/recipients/{id}
Action
List mailing listsList all mailing lists. GET /mailing_lists
Action
List recipientsList all recipients in a mailing list. GET /mailing_lists/{mailing_list}/recipients
Action
Send LetterWe'll print and mail out any content you provide us as a letter.
Action
Update mailing listUpdate a mailing list. POST /mailing_lists/{id}
Action
Update print jobUpdate an existing print job. POST /prints/{id}
Action
Update recipientUpdate a mailing list recipient. POST /mailing_lists/{mailing_list}/recipients/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.