Integration
Connect Intercom to Amberscript
When something happens in Intercom, 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 Intercom 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 Intercom and Amberscript
Triggers and actions 9 triggers · 39 actions
Trigger
New companyFires when a new company is created. Poll GET /companies ordered by created_at.
Trigger
New conversationPolls for conversations, most recently updated first. Fires for each new conversation.
Trigger
New leadInstant trigger: fires when a new lead is created in Intercom (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New note on conversationInstant trigger: fires when a note is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New or updated contactPolls for contacts, most recently updated first. Fires for each new or updated contact.
Trigger
New tag on a conversationInstant trigger: fires when a tag is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New tag on a userInstant trigger: fires when a tag is added to an Intercom user (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New ticketFires when a new ticket is created. Poll GET /tickets/search or /tickets ordered by created_at.
Action
Add companyCreate (or upsert) a company in Intercom. POST /companies.
Action
Add note to contactAdds a note to the specified contact as the specified admin.
Action
Add note to conversationAdds an internal note to the specified conversation as an admin.
Action
Add tag to contactAttaches a tag to the specified contact.
Action
Add ticketCreate a support ticket. POST /tickets.
Action
Assign conversationAssigns the conversation to an admin or team.
Action
Close conversationCloses the specified conversation.
Action
Create contactCreates a new contact (role user or lead) in Intercom.
Action
Create messageCreates an admin-initiated email or in-app message to a contact.
Action
Delete companyDelete a company by ID. DELETE /companies/{company_id}.
Action
Delete contactDeletes a contact by ID.
Action
Find admin by emailFetches an admin's details. Lists all admins; match by email.
Action
Find contact by emailSearches contacts by email and returns matches.
Action
Find ticketsSearch tickets by criteria. POST /tickets/search.
Action
Get companyRetrieve a company by ID. GET /companies/{company_id}.
Action
Get contactFetches a contact's details by ID.
Action
Get conversationFetches a conversation's details by ID.
Action
Get ticketRetrieve a ticket by ID. GET /tickets/{ticket_id}.
Action
List companiesList all companies. GET /companies.
Action
List segmentsList all segments. GET /segments.
Action
List tagsLists all tags for the workspace.
Action
Open conversationOpens (marks open) the specified conversation.
Action
Remove tag from contactDetaches a tag from the specified contact.
Action
Send conversation replySends a reply to the specified conversation as an admin.
Action
Snooze conversationSnoozes the specified conversation until the given unix timestamp.
Action
Start conversationStarts a new conversation with the specified contact.
Action
Track eventSubmit a data event for a contact. POST /events.
Action
Update companyUpdate an existing company. PUT /companies/{company_id}.
Action
Update contactUpdates an existing contact specified by ID.
Action
Update ticketUpdate an existing ticket. PUT /tickets/{ticket_id}.
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.