Integration
Connect SQL Server to Amberscript
When something happens in SQL Server, 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 SQL Server 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 SQL Server and Amberscript
Triggers and actions 5 triggers ยท 16 actions
Trigger
New or Updated RowTriggers when a new row is added or modified.
Trigger
New or Updated Row (Custom Query)Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.
Trigger
New RowTriggers when you add a new row.
Trigger
New TableFires when a new table appears in the connected SQL Server database.
Action
Add RowAdd one row to a table on the connected SQL Server database.
Action
Delete RowDelete the rows in a table whose chosen column equals a value.
Action
Find RowFind the first row in a table whose chosen column matches a value.
Action
Find Rows via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns every row it matches.
Action
Find Row via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
Action
Run Custom StatementRuns a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.
Action
Update RowChange column values on every row of a table whose chosen column matches a value.
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.