Printify + Google Sheets: consistent listings fast
Your Printify catalog grows, your listings get messy, and suddenly every “quick tweak” turns into a copy-paste marathon. Titles drift off-brand. Descriptions get inconsistent. And it’s way too easy to update the wrong product.
This is the kind of problem that hits ecommerce managers first, but marketers and agency teams cleaning up client stores feel it too. With Printify Sheets automation, you can generate consistent titles and descriptions, review them in one place, and only publish what you approve.
Below, you’ll see how the workflow runs, what it changes inside Printify, and how Google Sheets becomes your approval layer and change log.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Printify + Google Sheets: consistent listings fast
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Printify - Get Shops"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Printify - Get Products"]
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Out", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split - id, title, desc", pos: "b", h: 48 }
n6@{ icon: "mdi:wrench", form: "rounded", label: "Calculator", pos: "b", h: 48 }
n7@{ icon: "mdi:wrench", form: "rounded", label: "Wikipedia", pos: "b", h: 48 }
n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Brand Guidelines + Custom In..", pos: "b", h: 48 }
n12@{ icon: "mdi:database", form: "rounded", label: "GS - Add Product Option", pos: "b", h: 48 }
n13@{ icon: "mdi:database", form: "rounded", label: "Update Product Option", pos: "b", h: 48 }
n14@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If1", pos: "b", h: 48 }
n15@{ icon: "mdi:swap-vertical", form: "rounded", label: "Number of Options", pos: "b", h: 48 }
n16["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Calculate Options"]
n17@{ icon: "mdi:swap-vertical", form: "rounded", label: "Remember Options", pos: "b", h: 48 }
n18@{ icon: "mdi:robot", form: "rounded", label: "Generate Title and Desc", pos: "b", h: 48 }
n14 --> n4
n14 --> n12
n3 --> n4
n7 -.-> n18
n6 -.-> n18
n4 --> n5
n17 --> n16
n16 --> n14
n15 --> n16
n1 --> n2
n13 --> n17
n12 --> n18
n18 --> n13
n2 --> n3
n5 --> n15
n0 --> n9
n9 --> n1
end
subgraph sg1["Google Sheets Flow"]
direction LR
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Printify - Update Product"]
n10@{ icon: "mdi:play-circle", form: "rounded", label: "Google Sheets Trigger", pos: "b", h: 48 }
n11["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Printify - Get Shops1"]
n19@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
n19 --> n11
n10 --> n19
n11 --> n8
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0,n10 trigger
class n18 ai
class n6,n7 ai
class n14,n19 decision
class n12,n13 database
class n1,n2,n8,n11 api
class n16 code
classDef customIcon fill:none,stroke:none
class n1,n2,n16,n8,n11 customIcon
The Problem: Catalog copy becomes unmanageable
Product titles and descriptions look simple until you have 100+ listings across multiple shops and seasonal campaigns. One day you’re standardizing “Tee” vs “T-Shirt,” the next you’re rewriting half the catalog because your brand voice changed. Doing it manually in Printify is slow, and doing it in a doc first is risky because there’s no guaranteed match between the text you wrote and the product you update. And if you don’t keep a change log, you’ll be guessing later which version actually performed better. Honestly, it becomes a game of “hope I didn’t break anything.”
The friction compounds fast. Here’s where it breaks down.
- Updating listings one by one encourages “good enough” copy instead of consistent, intentional copy.
- Small naming changes get missed, which means you end up with duplicates and mixed formatting across the same product line.
- Without a review step, AI help can backfire because you push text live before it matches your brand rules.
- When performance drops, you can’t trace what changed because the history lives in scattered notes and browser tabs.
The Solution: Generate, review, then publish updates
This workflow pulls your shops and products from Printify, breaks the catalog into manageable batches, and then uses OpenAI to draft improved titles and descriptions based on your brand guidelines. Instead of pushing updates straight to your store, it writes every proposed change into Google Sheets with the old copy right next to the new copy. That gives you a clean approval queue and a built-in audit trail. When you’re ready, you approve specific rows in the sheet, and the workflow updates only those products back in Printify. It’s a controlled pipeline: generate, review, and publish, without losing track of what changed.
The workflow starts with a manual run (handy for testing) to fetch stores and product data via HTTP requests to Printify. It drafts new copy with OpenAI, logs everything to Google Sheets, then waits for a Google Sheets row update to trigger the final “approved” publish back to Printify.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you want to refresh 50 products before a seasonal push. Manually, you might spend about 6 minutes per product to open the listing, rewrite the title, polish the description, and double-check you’re editing the right item. That’s roughly 5 hours, and it’s easy to lose another hour fixing inconsistencies. With this workflow, you run one job to generate drafts and populate Google Sheets, then spend about 1–2 minutes per row approving or tweaking. You’re usually done in about 2 hours, with a clean record of every change.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Printify for product catalog access and updates
- Google Sheets to review, approve, and log changes
- OpenAI API key (get it from the OpenAI API dashboard)
Skill level: Intermediate. You’ll connect credentials and edit a few fields like sheet names, prompts, and API headers.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You start the run (or schedule it later). The workflow can be kicked off manually for testing, which is useful when you’re dialing in brand instructions and checking output quality.
Printify data is pulled and prepared. n8n retrieves your store list, fetches the full product catalog, then expands the results into individual product records so each item can be processed cleanly.
AI drafts new copy in batches. Products move through a loop in manageable chunks, and OpenAI generates a rewritten title and description using your “Brand Rules & Notes.” The workflow can also check option limits (like variant counts) so problematic items don’t derail the whole run.
Google Sheets becomes the control panel. For each product, the workflow appends a row with old text, new text, and fields that support review. When you flip an approval flag in the sheet, a Google Sheets trigger fires and the workflow updates the corresponding product back in Printify.
You can easily modify the brand guidelines prompt to match different product categories, then keep the same approval flow in Sheets based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Configure the Manual Trigger
This workflow starts manually for catalog processing and also listens for Google Sheets row updates to push approved changes back to Printify.
- Add Manual Start Trigger as the entry point for the catalog processing path.
- Add Sheet Row Trigger and set Event to
rowUpdate. - In Sheet Row Trigger, set Columns to Watch to
uploadand Poll Times toeveryMinute. - Credential Required: Connect your googleSheetsTriggerOAuth2Api credentials to Sheet Row Trigger.
Connect Printify API
These nodes pull your store list and product catalog from Printify for downstream processing.
- In Retrieve Store List, set URL to
https://api.printify.com/v1/shops.json. - Credential Required: Connect your httpHeaderAuth credentials to Retrieve Store List.
- In Fetch Product Catalog, set URL to
=https://api.printify.com/v1/shops/{{ $json.id }}/products.json. - Credential Required: Connect your httpHeaderAuth credentials to Fetch Product Catalog.
Set Up Data Expansion and Option Counting
This section expands the product catalog and loops through items while controlling how many options are processed.
- In Expand Records, set Field To Split Out to
datato expand the product list. - Use Iterate Items to batch through items coming from Expand Records.
- In Extract ID Title Desc, set Field To Split Out to
idand Fields To Include totitle, description. - In Set Option Count, set number_of_options to
3. - In Compute Option Total, keep Mode as
runOnceForEachItemand paste the provided JavaScript from the workflow to computenumber_of_optionsandresult. - In Check Option Limit, set the condition left value to
={{ $json.result }}and right value to0with Equals to control loop exit.
Set Up Draft Title & Description
This step drafts new product titles and descriptions using OpenAI and brand rules.
- In Brand Rules & Notes, set brand_name to
Your Brand, brand_tone toinformal, instructional, trustoworthy, and custom_instructions tore-write for the coming Christmas season. - In Draft Title & Description, set Model to
gpt-4o-miniand enable JSON Output. - Ensure the prompt references the expressions for product data, like
{{ $('Extract ID Title Desc').item.json.title }}and{{ $('Extract ID Title Desc').item.json.description }}, and brand rules like{{ $('Brand Rules & Notes').item.json.brand_name }}. - Credential Required: Connect your openAiApi credentials to Draft Title & Description.
- Wiki Lookup and Math Helper are AI tools connected to Draft Title & Description; add credentials on Draft Title & Description (not on the tools) if required by your environment.
Configure Google Sheets Outputs
The workflow appends a processing row, then updates it with AI-generated content.
- In Append Sheet Entry, set Operation to
append, and select your spreadsheet in Document ID and Sheet Name. - Map columns in Append Sheet Entry using expressions like
={{ Math.random().toString(36).substr(2, 12) }}for xid and={{ new Date().toISOString().split('T')[0] }}for date. - Credential Required: Connect your googleSheetsOAuth2Api credentials to Append Sheet Entry.
- In Update Sheet Option, set Operation to
appendOrUpdateand set Matching Columns toxid. - Map AI outputs in Update Sheet Option, such as keyword to
={{ $json.message.content.keyword }}and product_title to={{ $json.message.content.title }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials to Update Sheet Option.
Configure the Printify Update Path
This path activates when a sheet row is marked for upload, then updates the product in Printify.
- In Upload Flag Check, set the condition left value to
={{ $json.upload }}and right value toyeswith Equals. - In Retrieve Store List B, set URL to
https://api.printify.com/v1/shops.json. - Credential Required: Connect your httpHeaderAuth credentials to Retrieve Store List B.
- In Modify Product Details, set URL to
=https://api.printify.com/v1/shops/{{ $json.id }}/products/{{ $('Sheet Row Trigger').item.json.product_id }}.jsonand Method toPUT. - Set the body parameters in Modify Product Details to
title={{ $('Sheet Row Trigger').item.json.product_title }}anddescription={{ $('Sheet Row Trigger').item.json.product_desc }}. - Credential Required: Connect your httpHeaderAuth credentials to Modify Product Details.
Test and Activate Your Workflow
Run through both the manual catalog path and the sheet update path to validate everything before turning it on.
- Click Execute Workflow on Manual Start Trigger to fetch products and populate the sheet.
- Verify that Append Sheet Entry creates a new row with
Product Processingstatus and that Update Sheet Option updates the same row usingxid. - Manually set a sheet row’s upload value to
yesand confirm Modify Product Details receives aPUTwith the new title and description. - When successful, switch the workflow to Active so Sheet Row Trigger runs continuously in production.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n credential test and the sheet sharing settings first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About an hour if your keys and sheet are ready.
No. You’ll mainly connect accounts and edit a few fields like the sheet name and your brand prompt.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per batch depending on catalog size.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Update the “Brand Rules & Notes” node to include category-specific rules (fit, materials, occasions, sizing notes), then adjust the “Draft Title & Description” prompt so it follows that structure every time. Common tweaks include adding a short benefits bullet list to the description, enforcing a max title length, and inserting seasonal phrasing without sounding spammy. If you want separate styles per category, split the catalog by tags and route each group to a different prompt.
Usually it’s an API key or header issue in the HTTP Request nodes. Regenerate your Printify API key, confirm it’s added to the right n8n credential type (HTTP header auth), then re-test the “Retrieve Store List” call. If the store list works but updates fail, your endpoint or product ID mapping may be off because the sheet row doesn’t match the item being updated. Rate limits can also show up when you process a large catalog in one run, so smaller batches help.
A few hundred products per run is realistic on most setups, and batching keeps it stable.
For this use case, n8n is usually the better fit because it handles loops, batching, and conditional approvals without turning into an expensive chain of tasks. The Google Sheets “review then publish” pattern is also easier to keep tidy when you can branch freely and re-run parts of the workflow. Zapier or Make can still work if your catalog is small and you only need basic rewriting, but the moment you want a change log, an approval flag, and safe publishing, complexity shows up. If you’re unsure, use the workflow as a baseline and then decide what you want to maintain long term. Talk to an automation expert if you’re not sure which fits.
Once this is running, catalog copy stops being a recurring fire drill. You approve the changes you like, publish with confidence, and keep moving.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
