Connect Readwise to Amberscript

Both apps 23Readwise 13Amberscript 10

• Trigger
  Any Document Created (Readwise Reader)

  Triggers when a new Document is created in Reader.

• Trigger
  Document Archived (Readwise Reader)

  Triggers when user archive Reader document.

• Trigger
  Document Finished (Readwise Reader)

  Triggers when user finishes reading the document in Reader (reaches 99% article done).

• Trigger
  Document Moved to Inbox (Readwise Reader)

  Triggers when user moves document to inbox.

• Trigger
  Document Moved to Later (Readwise Reader)

  Triggers when user moves Reader document to later section.

• Trigger
  Document Shortlisted (Readwise Reader)

  Triggers when user shortlists a document in Reader.

• Trigger
  Document Tags Updated (Readwise Reader)

  Triggers when user updates tags in a Reader document.

• Trigger
  Feed Document Created (Readwise Reader)

  Triggers when a new (feed) Document is created in Reader.

• Trigger
  Highlight Created (Readwise)

  Triggers when a new highlight has been created in Readwise.

• Trigger
  Highlight Tag Created (Readwise)

  Triggers when user added a tag to a highlight.

• Trigger
  Non Feed Document Created (Readwise Reader)

  Triggers when a new (non feed) Document is created in Reader.

• Action
  Add Document (Readwise Reader)

  Add Document to Reader

• Action
  Create Highlight (Readwise)

  Create a new highlight in Readwise.

• Trigger
  Job Finished

  Triggers when a job has finished on our platform.

• Action
  Add glossary

  Create 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 Job

  This action creates a new job on the Amberscript platform.

• Action
  Delete glossary

  Delete an existing glossary. DELETE https://api.amberscript.com/api/glossaries/{glossaryId}?apiKey={apiKey}.

• Action
  Delete job

  Delete a transcription job. DELETE https://api.amberscript.com/api/jobs?jobId={jobId}&apiKey={apiKey}. Returns {"message":"Job deleted"}.

• Action
  Get job

  Retrieve 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 transcript

  Download 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 glossaries

  List 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 jobs

  List all transcription jobs for the account. GET https://api.amberscript.com/api/jobs?apiKey={apiKey}. Returns an array of jobStatus objects.

• Action
  Update glossary

  Update 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.