Automations worth building once — and why most workflow packs are not

Somebody sells you 2,000 workflow templates for $20. You spend an evening importing them, hit a node error on the third one, and find out it also needs a $9-a-month subscription and a developer account you do not have. That is not automation. That is a project you never agreed to take on.

I looked hard at this category before deciding not to build in it. Here is what I use instead.

The test I run before automating anything

Three questions. A task must pass all three.

1. Does it depend on somebody else's release schedule? If a vendor can ship an update that breaks your setup while you sleep, you did not build it. You adopted it.
2. Does it need credentials that expire, rotate, or get re-entered by hand? Every connection is a future failure with your name on it.
3. Would I still want this at ten times my current volume? If no, the task is too rare to justify tooling.

Most of what gets sold as "Etsy automation" fails the first question. n8n shipped version 2.0 in December 2025 with a long list of breaking changes: the Start node removed, the Pyodide Python Code node removed, ExecuteCommand and LocalFileTrigger disabled by default, environment-variable access blocked inside the Code node, and MySQL and MariaDB dropped. A pack built before that December and never touched since has pieces that no longer run, and nothing in the file tells you which ones.

Make.com fails on the second question. A blueprint arrives without its account connections attached. A thread in Make's own forum has a buyer signing in to 27-plus modules one after another to get an imported scenario running; further down, somebody says rebuilding from scratch turned out quicker.

If a thing needs maintaining, you did not build it once. You hired it.

Do the arithmetic before you do the workflow

Published pricing, checked July 2026.

• Make.com free tier: 1,000 credits a month, only two active scenarios, 15-minute minimum interval. The meter counts every step, so filters and routers that return nothing still spend your allowance.
• Make paid: Core $9/mo, Pro $16/mo, Teams $29/mo on annual billing, all from 10,000 credits a month.
• n8n Cloud: roughly $24/mo at the starter tier, or self-host and own the VPS, Docker and upgrades yourself.
• AI API keys: metered separately, on top.

Put numbers on your own situation. A shop doing 20 orders a month, running a workflow that saves two minutes per order, is buying back 40 minutes a month for $108 a year, before setup time and API metering. At 400 orders a month that trade looks different. At 20 it usually does not, and no sales page will run that sum for you.

One more wall, specific to this audience. n8n has no native Etsy node; the feature request has been open for years. Make does have a full Etsy app, but connecting it needs your own client ID and secret from an approved