Integration
Connect Mailparser to ShipStation
When something happens in Mailparser, your agent does the next thing in ShipStation. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and ShipStation 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 Mailparser and ShipStation
Triggers and actions 3 triggers · 18 actions
Trigger
New Email Parsed (One Request Per Email)Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
- New Email Parsed (One Request Per Row)
Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
Trigger
New or Updated OrderPolling trigger: fires when an order is created or modified.
- Add Warehouse
Create a new warehouse location. POST /warehouses (ShipStation API v1).
- Create or Update Order
Create a new order or update an existing one (upsert by orderNumber/orderKey).
- Delete Order
Delete (deactivate) an order by its ShipStation order ID.
- Get Customer
Retrieve a single customer by customer ID.
- Get Order
Retrieve a single order by its ShipStation order ID.
- Get Product
Retrieve a single product by ID. GET /products/{productId} (ShipStation API v1).
- Get Rates
Get shipping rate estimates for a carrier between two locations and package.
- Get Store
Retrieve details of a single store by ID. GET /stores/{storeId} (ShipStation API v1).
- Get Warehouse
Retrieve details of a single warehouse by ID. GET /warehouses/{warehouseId} (ShipStation API v1).
- List Carriers
List the shipping carriers connected to the account.
- List Customers
List customers in the ShipStation account.
- List Orders
List orders, optionally filtered by status, customer, or modified date.
- List Products
List products in the ShipStation catalog.
- List Stores
Retrieve the list of stores connected to the account. GET /stores (ShipStation API v1).
- List Warehouses
List the ship-from warehouse locations configured in the account.
- Mark Order as Shipped
Mark an order as shipped with a carrier code and tracking number.
- Update Product
Update an existing product's details (SKU, name, price, weight, etc). PUT /products/{productId} (ShipStation API v1).
- Update Warehouse
Update an existing warehouse's name/address/return address. PUT /warehouses/{warehouseId} (ShipStation API v1).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.