FlowRunner
PricingContact
Theme
Start Free

Printify

E-commerce

Run a Printify print-on-demand shop from FlowRunner. Agents build products from catalog blueprints and print providers, publish them to connected sales channels like Shopify and Etsy, upload artwork, and submit orders to production.

14 actions API key available
Printify website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
A new order arrives from the connected storefront
Get Product resolves each line item to its Printify product, variant, and print provider
Create Order builds the order with recipient address, shipping method, and an external ID tied back to the storefront, held out of production by default
The agent validates the address, compares production cost against the retail price, and flags unusual quantities
Flagged orders wait: a person rules on the incomplete address, the negative-margin variant, the fifty-unit order from a new customer
Send Order To Production submits the approved orders for print and fulfillment
Get Order polls status until tracking information appears
The fulfillment log updates and the customer's tracking flows back to the storefront

What This Integration Enables

Print-on-demand removed inventory risk and quietly replaced it with process risk. Nothing exists until someone orders it, which means every order races straight toward production, and production is the moment mistakes become physical: printed, boxed, and shipped to a customer with your brand on the label. Printify's API separates creating an order from committing it, and FlowRunner is built around exactly that seam. Agents assemble products and orders at machine speed; the release into production is a governed step. - Mirror products from a feed or source system into a Printify shop, mapping catalog variants to retail prices and print files - Publish finished products to the connected sales channel: Shopify, Etsy, or an API shop - Create orders for existing products and submit them to production deliberately, not by default - Upload artwork server-side from a URL and place it onto product print areas - Browse blueprints and print providers to discover what can be made and where The blueprint and print provider catalog is itself workflow raw material: the same design can become twenty products by iterating List Blueprints and List Print Providers instead of twenty dashboard sessions.

Without FlowRunner

Listing a product is an afternoon Artwork, variants, prices, and publishing get assembled by hand in the dashboard, per product
Orders forwarded on faith Sales flow straight to production, and the bad address or loss-making variant is discovered after it ships
Fulfillment status lives in another tab Nobody knows an order stalled until the customer emails asking where it is

With FlowRunner

Products build from a feed Artwork uploads, product creation, and channel publishing chain from a spreadsheet row
Production is a decision, not a default Orders are created on hold, checked for margin and address quality, and released deliberately
Status flows to where the team looks Order states and tracking sync to the log and the channel automatically

Use Case Scenarios

A product line from a spreadsheet

The product feed lives in [Google Sheets](/integrations/google-sheets): design URL, product type, retail prices. For each row, the agent calls Upload Image to bring the artwork into the media library, Create Product against the chosen blueprint and print provider with variants priced from the sheet, and Publish Product to push it live to the connected channel. Twenty products go from rows to listings in one run, and the draft-then-publish sequence means nothing appears on the storefront half-built.

Orders fulfilled with a margin check in the loop

When a [Shopify](/integrations/shopify) order lands, the agent creates the matching Printify order with Create Order, then compares Printify's cost breakdown against what the customer paid. Healthy orders release immediately through Send Order To Production. Orders where a price change or shipping method turned the margin negative stop and post to [Slack](/integrations/slack) for a decision. The store stops discovering unprofitable SKUs in the monthly numbers.

The fulfillment board that stays current

On a schedule, List Orders pulls recent orders with their statuses, and Get Order fetches tracking for anything that moved. The agent appends progress to the tracking sheet, flags orders that have sat in the same status too long, and posts exceptions to the channel. When a customer writes in, support answers from the log instead of logging into Printify to find out what happened.

Human-in-Loop Highlight

Send Order To Production is the point of no return in this connector. Printify's API is explicit about it: once submitted, the order enters the production pipeline and can no longer be freely edited. Whatever was wrong when it crossed that line gets printed, boxed, and shipped to a customer. So FlowRunner treats Create Order and Send Order To Production as two different decisions. Orders are created on hold, and the agent checks what software can check: address completeness, cost against retail, quantity anomalies. Anything flagged waits for a person who sees the order detail from Get Order next to the reason it was held. Clean orders release automatically; judgment calls do not. The cost of the gate is a moment of review. The cost of skipping it is a misprinted batch with your brand on the return label.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

14 actions

Shops

1
  • List Shops Lists the shops connected to the account with their IDs, titles, and sales channels. Shop IDs anchor every product and order operation.

Products

6
  • List Products Retrieves a shop's products with titles, blueprint and print provider IDs, variants, images, and publishing status, paginated for large catalogs.
  • Get Product Retrieves one product's full detail: variants with prices, print areas with image placements, images, and publishing status. The resolution step between storefront line items and Printify variants.
  • Create Product Creates a draft product from a blueprint and print provider, with enabled variants, prices, and print areas referencing uploaded images. Publishing is a separate, deliberate step.
  • Update Product Updates a product's title, description, variants, prices, or print area placements, changing only the fields supplied.
  • Delete Product Permanently deletes a product from the shop and, if published, from the connected sales channel. Cannot be undone, so cleanup flows run it only after review.
  • Publish Product Pushes a product to its connected sales channel, with control over which parts sync: title, description, images, variants, tags, shipping template. Rate limited to 200 requests per 30 minutes, which batch flows respect by pacing.

Orders

4
  • List Orders Retrieves a shop's orders with status, line items, shipping, and totals, filterable by status. The read behind fulfillment tracking.
  • Get Order Retrieves one order's full detail: status, line items, recipient address, cost breakdown, and tracking once fulfillment starts.
  • Create Order Creates an order for existing products with line items, shipping method, and recipient address. Held from production by default, with an external ID to correlate back to your own system.
  • Send Order To Production Submits an order for production and shipping. Irreversible once accepted, and the operation this page's human gate exists for.

Catalog

2
  • List Blueprints Lists the catalog's base product types with brand, model, and preview images. The starting point for building any new product.
  • List Print Providers Lists the print facilities that can produce a given blueprint, each with its own variants, prices, and location. The sourcing decision expressed as data.

Media

1
  • Upload Image Uploads artwork to the Printify media library from a publicly accessible URL, returning the image ID that print areas reference in Create Product and Update Product.

Frequently Asked Questions

What can FlowRunner do with Printify?

FlowRunner agents can run List Shops, List Products, and Get Product in Printify, plus 11 more actions.

Does connecting Printify to FlowRunner require OAuth?

No. Printify connects to FlowRunner with an API key, no OAuth flow required.

Can Printify trigger a FlowRunner workflow automatically?

Printify doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Printify

$100 in credits. No card required. Connect in minutes.