Integration

Connect Heartbeat to Simpleen Translation

When something happens in Heartbeat, your agent does the next thing in Simpleen Translation. Describe it in plain language and the automation is built, tested on every branch and kept running.

Heartbeat4 triggersHeartbeat6 actionsSimpleen Translation13 actions

Browse all apps

Build it

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

Triggers and actions 4 triggers · 19 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.
Action
Add glossary
Create a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segment
Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create Translation
Translates content to selected target language
Action
Get file
Get a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossary
Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segment
Get a specific translation segment by id. GET /segments/{id}.
Action
List files
List the localization files known to the account. GET /files.
Action
List glossaries
List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languages
List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segments
List translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translator
Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossary
Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segment
Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.

Each app on its own

The other way round: Simpleen Translation to Heartbeat