Integration
Connect ShipStation to Simpleen Translation
When something happens in ShipStation, your agent does the next thing in Simpleen Translation. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want ShipStation and Simpleen Translation 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 ShipStation and Simpleen Translation
Triggers and actions 1 trigger ยท 31 actions
Trigger
New or Updated OrderPolling trigger: fires when an order is created or modified.
Action
Add WarehouseCreate a new warehouse location. POST /warehouses (ShipStation API v1).
Action
Create or Update OrderCreate a new order or update an existing one (upsert by orderNumber/orderKey).
Action
Delete OrderDelete (deactivate) an order by its ShipStation order ID.
Action
Get CustomerRetrieve a single customer by customer ID.
Action
Get OrderRetrieve a single order by its ShipStation order ID.
Action
Get ProductRetrieve a single product by ID. GET /products/{productId} (ShipStation API v1).
Action
Get RatesGet shipping rate estimates for a carrier between two locations and package.
Action
Get StoreRetrieve details of a single store by ID. GET /stores/{storeId} (ShipStation API v1).
Action
Get WarehouseRetrieve details of a single warehouse by ID. GET /warehouses/{warehouseId} (ShipStation API v1).
Action
List CarriersList the shipping carriers connected to the account.
Action
List CustomersList customers in the ShipStation account.
Action
List OrdersList orders, optionally filtered by status, customer, or modified date.
Action
List ProductsList products in the ShipStation catalog.
Action
List StoresRetrieve the list of stores connected to the account. GET /stores (ShipStation API v1).
Action
List WarehousesList the ship-from warehouse locations configured in the account.
Action
Mark Order as ShippedMark an order as shipped with a carrier code and tracking number.
Action
Update ProductUpdate an existing product's details (SKU, name, price, weight, etc). PUT /products/{productId} (ShipStation API v1).
Action
Update WarehouseUpdate an existing warehouse's name/address/return address. PUT /warehouses/{warehouseId} (ShipStation API v1).
Action
Add glossaryCreate a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segmentCreate a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create TranslationTranslates content to selected target language
Action
Get fileGet a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossaryGet a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segmentGet a specific translation segment by id. GET /segments/{id}.
Action
List filesList the localization files known to the account. GET /files.
Action
List glossariesList the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languagesList all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segmentsList translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translatorTranslate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossaryUpdate an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segmentPost-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.