Integration

Connect Nutshell to Wachete

When something happens in Nutshell, 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.

Nutshell6 triggersNutshell12 actionsWachete2 triggersWachete7 actions

Browse all apps

Build it

What do you want Nutshell 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 Code

Everything your agent can do with Nutshell and Wachete

Triggers and actions 8 triggers · 19 actions

Trigger
Activity Logged
Triggers when an Activity is logged.
Trigger
Lead Won
Triggers when a lead is won.
Trigger
New Activity
Triggers when new Activity is created.
Trigger
New Company
Triggers when new Company is created.
Trigger
New Lead
Triggers when a new Lead is created.
Trigger
New Person
Triggers when new Person is created.
Action
Create Company
Creates a new Company.
Action
Create Lead
Creates a new Lead.
Action
Create Person
Creates a new Person.
Action
Find Company
Finds an existing company.
Action
Find Lead
Finds an existing lead by a particular field. Defaults to searching open leads, falls back to all leads.
Action
Find Person
Finds an existing person.
Action
Find User
Finds an existing User.
Action
Log Activity
Creates and logs a new Activity.
Action
Update Company
Updates an existing Company.
Action
Update Lead
Updates an existing Lead.
Action
Update Lead Outcome
Updates a Lead Outcome.
Action
Update Person
Updates an existing Person.
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.

Each app on its own

The other way round: Wachete to Nutshell