Skip to main content

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

Register now (opens in a new tab)
Printify
Tally

Connect Printify and Tally

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

Get started free

Create a custom workflow

Integrate Printify 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
Printify
Action: Select an action
1. Select a trigger

  • Triggers when a new form response is submitted.

2. Select an action

  • Archive an uploaded image.

  • Cancels an unpaid order. The request will only be accepted if the order to be canceled has the status "on-hold" or "payment-not-received".

  • Creates a new product.

  • Deletes a product.

  • Disconnects a shop.

  • Returns a specific blueprint.

  • Returns a product.

  • Returns a specific print provider and a list of associated blueprint offerings.

  • Returns an image.

  • Returns order details by ID.

  • Returns shipping information.

  • Returns shipping cost of an order.

  • Performs an arbitrary authorized API call.

  • Publishes a product.

  • Sends to production

  • Removes the product from the locked status on the Printify app.

  • Removes the product from the locked status on the Printify app and sets its external property with the handle you provide in the request body.

  • Orders an existing product.

  • Updates a product.

  • Uploads image files either via image URL or image file base64-encoded contents. The file will be stored in the Merchant's account Media Library.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Printify and Tally.

Archive an Uploaded Image
Archive an uploaded image.
Action
Cancel an Order
Cancels an unpaid order. The request will only be accepted if the order to be canceled has the status "on-hold" or "payment-not-received".
Action
Create a Product
Creates a new product.
Action
Delete a Product
Deletes a product.
Action
Delete a Shop
Disconnects a shop.
Action
Get a Blueprint
Returns a specific blueprint.
Action
Get a Product
Returns a product.
Action
Get a Provider
Returns a specific print provider and a list of associated blueprint offerings.
Action
Get an Image
Returns an image.
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.