Integration
Connect ShipStation to Amplitude
When something happens in ShipStation, your agent does the next thing in Amplitude. 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 Amplitude 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 Amplitude
Triggers and actions 1 trigger ยท 30 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
Batch upload eventsSends a batch of events to Amplitude in one call. Use this when you have many events to record at once rather than one at a time.
Action
Export event dataExports every event Amplitude recorded in a time window, as a zip archive of event data.
Action
Get cohortReturns one behavioral cohort's details, including its name, size and when it was last recalculated.
Action
Get event segmentationCounts how often an event happened over a date range, optionally split by a property or filtered to a segment of users.
Action
Get funnel analysisRuns a funnel over a series of events and returns how many users reached each step and how many dropped off.
Action
Get retention analysisShows how many users came back and did something again after a starting event, over a date range.
Action
Get user propertiesLooks a user up in Amplitude and returns what Amplitude knows about them, including their Amplitude ID.
Action
Group identifySets properties on a group in Amplitude, such as a company or team, so you can analyse behaviour by group.
Action
Identify userSets properties on a user in Amplitude without recording an event, so later events are attributed with the new details.
Action
List cohortsLists every behavioral cohort in the Amplitude project, with each cohort's name, size and owner.
Action
Send eventRecords a single event in Amplitude for a user, with optional event and user properties.
Action
Upload cohortCreates a cohort in Amplitude from a list of users you supply.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.