What to Know Before You Install Etsy Automation Blueprints

Most Etsy automation setups don’t fail because the automation is wrong. They fail because of the order things were done in, and because of a handful of errors that look fatal but aren’t.

This is what I wish someone had told me before the first install.

Install one scenario at a time

The system is four Make.com scenarios that hand work to each other. It’s tempting to import all four, then wire everything up in one pass.

Don’t. Import one, save it, then move to the next.

The reason is that scenarios can only reference each other once they exist. If you import all four and start connecting, half your dropdowns will be empty, and you’ll assume something is broken when the scenario you’re pointing at simply hasn’t been saved yet.

Save before you connect anything

This is the single most useful habit, and it feels wrong the first time.

When you import a blueprint, Make will often show errors immediately — modules with warnings, fields it can’t resolve, connections it doesn’t recognise. The instinct is to fix those before saving.

Save anyway.

A freshly imported scenario is supposed to look unhappy. It’s referencing accounts you haven’t authorised and sheets you haven’t picked yet. Saving it registers the scenario so other scenarios can see it, and it gives you a stable thing to come back to. Fix afterwards.

Red dots are usually just missing connections

A red dot on a module means Make can’t complete that step as configured. In a fresh install that’s almost always one of three things:

1. The account isn’t connected. You haven’t authorised Google, OpenAI or Etsy for that module yet.
2. The dropdown is stale. Make cached the list before your folders existed. Hit refresh on the dropdown and the option appears.
3. The sheet or folder was renamed. The blueprint points at a name that no longer matches.

None of those mean the blueprint is broken. Open the module, reconnect, refresh the dropdown, save. The dot clears.

What a red dot almost never means is that you need to rebuild the scenario. If you find yourself deleting modules on day one, stop and check the connection first.

Scenario Call replaced the old webhook chaining

This one catches people following older tutorials.

Make.com used to require webhooks to pass work between scenarios: scenario one fires a webhook, scenario two listens for it, and you copy URLs between them by hand. A lot of automation content still teaches this, including some of the earlier lessons in this series.

Make now has Scenario Call modules, which do the same job without the URL copying. They’re cleaner, they survive being edited, and they’re much easier to debug because you can see which scenario is calling which.

If you’re following along with older material and it tells you to paste a webhook URL between scenarios, that step has largely gone away. The one place a traditional webhook still applies is the very first flow in the chain, which has to be triggered by something outside Make.

Get the folder structure right first

The blueprints expect a specific Google Drive layout, and they expect it to exist before they run.

The structure is a top-level folder holding collections, then a folder per shop type, then a folder per product named with its SKU. It looks over-organised for the first product and obviously correct by the twentieth.

Two reasons it matters more than it looks:

• The automation finds files by path. If a folder is missing, the scenario doesn’t improvise — it errors.
• The SKU folder is how everything stays matched. Images, the customer PDF and the listing data all reference the same SKU. That’s what keeps product 40’s images out of product 41’s listing.

Build the folders first, then import. Doing it the other way round means reconnecting every module afterwards.

The document location setting that breaks the PDF

There’s one error that’s worth knowing in advance because it’s non-obvious: the customer download PDF failing because the template isn’t where the scenario expects.

The template document has to sit inside the docs folder of your automation structure. If you created it somewhere convenient — your Drive root, or a folder you made for it — the PDF step fails with an error that doesn’t obviously say “wrong folder.”

Move the template into the docs folder and it resolves.

Reconnecting a spreadsheet properly

When you reconnect a Google Sheets module, do all three of these, in order:

1. Choose the connection.
2. Refresh the spreadsheet dropdown, then pick the file.
3. Refresh the sheet dropdown, then pick the tab.

Skipping the refreshes is what causes the “I picked the right sheet and it still fails” problem. Make is showing you a cached list, and the entry you clicked isn’t the one it stored.

What actually goes wrong, honestly

Automations are powerful and they do break. Apps change their APIs, permissions expire, a Google account gets logged out, a sheet gets renamed by someone tidying up.

When something stops working, the fix is nearly always the same: open the scenario, find the module with the error, reconnect it, save. It’s rarely a rebuild. The failures are boring, which is good news — boring failures have short fixes.

What you’re signing up for is not a system that never breaks. It’s a system that breaks in ways you can diagnose in five minutes instead of rebuilding by hand.

Before you start: what this costs to run

Worth knowing up front rather than at the import screen.

The system uses four Make.com scenarios. Make’s free plan allows two active scenarios, so the free tier cannot run this at all — you’ll need their cheapest paid tier. You’ll also need your own OpenAI API key, billed to you per listing.

The lessons are free. The files are free. The running cost is not, and anyone who tells you otherwise is hoping you won’t check.

If you’d rather not maintain a Make account at all, Elistit does the same pipeline from one sentence, and there’s a free plan to try it on.

Where the files live

Every lesson in this series is free and public on YouTube, install walkthroughs included. The blueprints, the Google Form and Sheets templates, the customer PDF layouts and the prompt library are in the free club — no card, no approval queue.

Join the club free and take the files with you.