Integration
Connect ShipStation to Browser Use
When New or Updated Order fires in ShipStation, your agent runs Upload workspace files in Browser Use. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want ShipStation and Browser Use to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What ShipStation can start in Browser Use
When New or Updated Order in ShipStation
then Upload workspace files in Browser Use
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with ShipStation and Browser Use
Triggers and actions 1 trigger · 28 actions
- New or Updated Order
Polling trigger: fires when an order is created or modified.
- Add Warehouse
Create a new warehouse location.
- 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 Rates
Get shipping rate estimates for a carrier between two locations and package.
- Get Store
Retrieve details of a single store by ID.
- Get Warehouse
Retrieve details of a single warehouse by ID.
- 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.
- 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).
- Update Warehouse
Update an existing warehouse's name/address/return address.
- Add profile
Create a new browser profile (persisted cookies/state) for reuse across runs.
- Add workspace
Create a new workspace for browser automation files and state.
- Delete profile
Delete a browser profile.
- Delete workspace
Delete a workspace.
- Get profile
Get the details of a specific browser profile.
- Get workspace
Get the details of a specific workspace.
- List workspace files
List files stored in a workspace.
- Update profile
Update a browser profile.
- Update workspace
Update a workspace's settings.
- Upload workspace files
Upload files into a workspace.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from ShipStation
ShipStation to PokéAPI (GraphQL)PokéAPI (GraphQL) is an unofficial GraphQL front end over the PokeAPI Pokemon dataset.
ShipStation to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
ShipStation to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ShipStation to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
ShipStation to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
ShipStation to MailchimpMailchimp marketing automation and email platform.
More into Browser Use
Webflow to Browser UseWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Slack to Browser UseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Questions
ShipStation and Browser Use, answered
What can start an automation from ShipStation?
Any of ShipStation's 1 trigger in the catalog, including New or Updated Order. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Browser Use when something happens in ShipStation?
Any of Browser Use's 10 actions, including Update profile, Update workspace, Upload workspace files and Add profile. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Browser Use to ShipStation?
Browser Use has no triggers in the catalog today, so automations start in ShipStation. If you need the other direction, ask: your agent reads Browser Use's API documentation and adds it.
Do I have to build a connector for ShipStation or Browser Use?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use ShipStation and Browser Use without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.