Integration

Connect Heartbeat to Wachete

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

Heartbeat4 triggersHeartbeat6 actionsWachete2 triggersWachete7 actions

Browse all apps

Build it

What do you want Heartbeat 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 Heartbeat and Wachete

Triggers and actions 6 triggers · 13 actions

Trigger
Abandoned Invitation Link
Triggers when someone enters their information in an invitation link, but does not make a purchase or create their account. This will trigger after 4 hours, if the user still has not made a purchase or created their account.
Trigger
Course Completed
Triggers when a user completes a course.
Trigger
New Event
Triggers when a new event is created.
Trigger
New Event RSVP
Triggers when someone RSVPs to an event.
Action
Create Event
Creates an event in a Heartbeat community and optionally invites people or groups.
Action
Create Group
Creates a group in a Heartbeat community, optionally nested under another group and seeded with members.
Action
Create Thread
Posts a new thread in a Heartbeat channel.
Action
Deactivate User
Removes a person's access to a Heartbeat community by email. Their threads, comments and messages stay in place.
Action
List Channels
Returns all channels in the Heartbeat community, with each channel's name, emoji and type.
Action
List Threads
Returns all threads posted in a Heartbeat channel, with each thread's body, author, link and creation time.
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 Heartbeat