Integration
Connect Heartbeat to Amberscript
When something happens in Heartbeat, your agent does the next thing in Amberscript. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Heartbeat and Amberscript 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 Heartbeat and Amberscript
Triggers and actions 5 triggers ยท 15 actions
Trigger
Abandoned Invitation LinkTriggers 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 CompletedTriggers when a user completes a course.
Trigger
New EventTriggers when a new event is created.
Trigger
New Event RSVPTriggers when someone RSVPs to an event.
Action
Create EventCreates an event in a Heartbeat community and optionally invites people or groups.
Action
Create GroupCreates a group in a Heartbeat community, optionally nested under another group and seeded with members.
Action
Create ThreadPosts a new thread in a Heartbeat channel.
Action
Deactivate UserRemoves a person's access to a Heartbeat community by email. Their threads, comments and messages stay in place.
Action
List ChannelsReturns all channels in the Heartbeat community, with each channel's name, emoji and type.
Action
List ThreadsReturns all threads posted in a Heartbeat channel, with each thread's body, author, link and creation time.
Trigger
Job FinishedTriggers when a job has finished on our platform.
Action
Add glossaryCreate a new glossary of terms that can be referenced by glossaryId on job upload for improved transcription accuracy. POST https://api.amberscript.com/api/glossaries?apiKey={apiKey}.
Action
Create New JobThis action creates a new job on the Amberscript platform.
Action
Delete glossaryDelete an existing glossary. DELETE https://api.amberscript.com/api/glossaries/{glossaryId}?apiKey={apiKey}.
Action
Delete jobDelete a transcription job. DELETE https://api.amberscript.com/api/jobs?jobId={jobId}&apiKey={apiKey}. Returns {"message":"Job deleted"}.
Action
Get jobRetrieve the status/details of a transcription job. GET https://api.amberscript.com/api/jobs/status?jobId={jobId}&apiKey={apiKey}. Returns jobStatus with status OPEN/BUSY/ERROR/DONE, transcriptionType, jobType, language, nrAudioSeconds, etc.
Action
Get job transcriptDownload a finished job's transcript/subtitles in a chosen export format. GET https://api.amberscript.com/api/jobs/export-{format}?jobId={jobId}&apiKey={apiKey} where format is one of srt, vtt, txt, json (srt/vtt take optional maxCharsPerRow/maxNumberOfRows/maxScreenTimePerRowSeconds; txt takes optional includeTimestamps/includeSpeakers/highlightsOnly/maxCharsPerRow). SRT/VTT/JSON return the content directly (JSON export returns structured word-level data); TXT and STL(deprecated) return a downloadUrl JSON wrapper for some formats. Implementer should expose a format field and branch the endpoint/response handling accordingly.
Action
List glossariesList all glossaries defined on the account (used to supply glossaryId when uploading a job). GET https://api.amberscript.com/api/glossaries?apiKey={apiKey} per Amberscript docs Glossary section.
Action
List jobsList all transcription jobs for the account. GET https://api.amberscript.com/api/jobs?apiKey={apiKey}. Returns an array of jobStatus objects.
Action
Update glossaryUpdate an existing glossary's terms. PUT/PATCH https://api.amberscript.com/api/glossaries/{glossaryId}?apiKey={apiKey}.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.