Integration
Connect Less Annoying CRM to Wachete
When something happens in Less Annoying CRM, your agent does the next thing in Wachete. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Less Annoying CRM and Wachete 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 Less Annoying CRM and Wachete
Triggers and actions 9 triggers · 17 actions
Trigger
Contact DeletionTriggers when a contact is deleted.
Trigger
Form SubmissionTriggers when a form submission is received.
Trigger
Group Membership AdditionTriggers when a contact is added to a group.
Trigger
Group Membership DeletionTriggers when a contact is removed from a group.
Trigger
New ContactTriggers when a new contact is created or a contact is updated.
Trigger
Pipeline Item DeletionTriggers when a pipeline item is deleted.
Trigger
Pipeline Item Status UpdateTriggers when a new pipeline item is added or its status is updated.
Action
Create ContactCreates a new contact.
Action
Create Contact NoteAdds a note to a contact.
Action
Create Group MembershipAdds a contact to a group.
Action
Create Pipeline ItemCreates a new pipeline item.
Action
Create TaskCreates a new task.
Action
Delete Group MembershipRemoves a contact from a group.
Action
Edit ContactEdit an existing contact. Blank fields will not be updated.
Action
Edit Pipeline ItemEdit an existing pipeline item attached to a contact.
Action
Find ContactSearch for contact by email, name, or LACRM Contact Id.
Action
Find Pipeline ItemSearch for a pipeline item.
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.
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