Connect Jumpseller to Simpleen Translation

Both apps 36Jumpseller 23Simpleen Translation 13

• 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

• Action
  Add glossary

  Create a new glossary of word entries/ignored terms for translation. POST /glossaries.

• Action
  Add segment

  Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.

• Action
  Create Translation

  Translates content to selected target language

• Action
  Get file

  Get a specific localization file by id, including its segments and languages. GET /files/{id}.

• Action
  Get glossary

  Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.

• Action
  Get segment

  Get a specific translation segment by id. GET /segments/{id}.

• Action
  List files

  List the localization files known to the account. GET /files.

• Action
  List glossaries

  List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.

• Action
  List languages

  List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.

• Action
  List segments

  List translatable segments (source/translated entry pairs) across the user's files. GET /segments.

• Action
  Run translator

  Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.

• Action
  Update glossary

  Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.

• Action
  Update segment

  Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.