Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
ShipStation
Tally

Connect ShipStation and Tally

Explore ready-made ShipStation and Tally templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate ShipStation with Tally and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Tally
Trigger: Watch New Responses
ShipStation
Action: Select an action
1. Select a trigger

  • Triggers when a new form response is submitted.

2. Select an action

  • Adds funds to a carrier account using the payment information on file.

  • Adds a tag to an order.

  • Assigns a user to an order.

  • Creates a new order.

  • Creates a new warehouse (Ship From Location).

  • Deactivates the specified store.

  • Removes a selected order from ShipStation's UI. This is a "soft" delete action so the order will still exist in the database, but will be set to "inactive".

  • Gets a selected carrier's details.

  • Gets a selected customer's details.

  • Retrieves a single order from the database.

  • Gets a selected product's details.

  • Gets a selected store's details.

  • Returns details for a selected warehouse (Ship From Location).

  • Changes the status of the given order to On Hold until the date specified.

  • Performs an arbitrary authorized API call.

  • Marks an order as shipped without creating a label in ShipStation.

  • Reactivates the specified store.

  • Initiates a store refresh.

  • Removes a tag from the specified order.

  • Changes the status of the given order from On Hold to Awaiting Shipment.

  • Unassigns a user from an order.

  • Updates an existing order. Only orders in an open status in ShipStation (awaiting_payment, awaiting_shipment, and on_hold) can be updated through this method. This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.

  • Updates an existing product. This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.

  • Updates an existing, active store. Inactive stores cannot be modified via the API. This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.

  • Updates an existing warehouse (Ship From Location). This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.

  • Voids the specified label by shipmentId.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between ShipStation and Tally.

Add Funds
Adds funds to a carrier account using the payment information on file.
Action
Add Tag to Order
Adds a tag to an order.
Action
Assign User to Order
Assigns a user to an order.
Action
Create Order
Creates a new order.
Action
Create Warehouse
Creates a new warehouse (Ship From Location).
Action
Deactivate Store
Deactivates the specified store.
Action
Delete Order
Removes a selected order from ShipStation's UI. This is a "soft" delete action so the order will still exist in the database, but will be set to "inactive".
Action
Get Carrier
Gets a selected carrier's details.
Action
Get Customer
Gets a selected customer's details.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.