Connect Jumpseller to Amberscript

Both apps 33Jumpseller 23Amberscript 10

• Trigger
  Customer Created

  Triggers when a new customer registers into the store.

• Trigger
  Customer Updated

  Triggers when a customer is updated.

• Trigger
  Order Paid

  Triggers when a new order is paid.

• Trigger
  Order Updated

  Triggers when an order status is updated (from an initial "pending payment" to either a "paid", "canceled" or "abandoned" status).

• Trigger
  Product Created

  Triggers when a new product is created.

• Trigger
  Product Updated

  Triggers when a product is updated.

• Action
  Add Category

  Create a new Category. POST /categories.json

• Action
  Add Customer

  Adds a new customer to your Jumpseller store.

• Action
  Create Product

  Creates a Product

• Action
  Create Product Variant

  Creates a new Product Variant

• Action
  Delete Customer

  Delete an existing Customer. DELETE /customers/{id}.json

• Action
  Delete Product

  Delete an existing Product. DELETE /products/{id}.json

• Action
  Find Customer From Email

  Finds a customer in your Jumpseller store by their email address.

• Action
  Find Product

  Finds a Jumpseller Product, returning the full product details (including its variants)

• Action
  Find Product From SKU

  Finds a product given a SKU, ID or Barcode

• Action
  Get Customer

  Retrieve a single Customer by id. GET /customers/{id}.json

• Action
  Get Product

  Retrieve a single Product by id. GET /products/{id}.json

• Action
  List Categories

  Retrieve all Categories. GET /categories.json

• Action
  List Customers

  Retrieve all Customers. GET /customers.json

• Action
  List Products

  Retrieve all Products in the store. GET /products.json (supports category/status filters and pagination).

• Action
  Update Customer

  Updates an existing customer in your Jumpseller store.

• Action
  Update Product

  Updates a Product

• Action
  Update Product by SKU

  Updates a product given a SKU

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