How to Create Etsy Draft Listings Automatically (Without Publishing Anything)

The final step of an automated Etsy workflow is the one people are most nervous about: letting software touch their actual shop.

That nervousness is reasonable, and the answer to it is simple. The automation creates drafts. Nothing publishes, nothing charges a listing fee, and nothing goes live until you read it and press the button yourself.

Here’s what that last step actually does.

What the draft step receives

By the time this runs, the earlier steps have already produced:

• the listing copy — title, tags, description, alt text
• the images, sorted and named in display order
• the digital files, in the product’s folder
• the customer download PDF

The draft step’s whole job is assembly: take those pieces and put them into Etsy’s listing fields in the right places.

Connecting Etsy to Make.com

You authorise Make against your Etsy shop once. Etsy asks what access you’re granting, you approve it, and the connection is available to every module that needs it.

Two things worth knowing:

The connection is per-shop. If you run more than one Etsy shop, you’re connecting the one you’re currently signed into. Check which shop you’re in before authorising.

Re-authorisation happens. Etsy connections expire, and when they do the automation fails at this last step with an authorisation error. It looks alarming because it’s the step touching your shop, but the fix is reconnecting the module — not rebuilding anything.

Mapping the fields

This part is repetitive and worth doing carefully, because it’s where silent mistakes hide.

Each module needs its account selected and its dropdown refreshed before you pick a value. Refreshing matters: Make shows a cached list, and the entry you click may not be the one it stores if the list is stale. If a field seems right but the run disagrees, this is usually why.

Work left to right through the scenario, opening each module, confirming the connection, refreshing, selecting, saving. It’s dull. It’s also the difference between an automation that works on product one and one that works on product fifty.

Price: the field to leave manual

Most people leave price out of the automated flow and set it on the draft.

That’s the right default. Price is the field you’re most likely to want to think about per product — introductory pricing, bundle discounts, seasonal adjustments — and it’s the one where an automated mistake costs actual money rather than time.

It can be automated, and if you sell a very consistent catalogue that’s fine. But of everything in the pipeline, this is the last thing I’d hand over.

Images and alt text

The image modules pull from the product’s Drive folder in the order the naming convention set, and upload them to the draft in that order.

Alt text is generated alongside the listing copy. It’s worth caring about for two reasons: it’s an accessibility baseline, and Etsy’s search reads it. It costs nothing extra here because the copy step already produced it.

Get an email when the run finishes

Optional, and worth switching on.

Add a Gmail module at the end of the scenario and let Make update its permissions when it asks. You get a message when the whole chain completes, sent to whichever inbox you use for shop admin.

The value isn’t the notification itself — it’s that a run which doesn’t email you is a run that failed somewhere, and you find out the same day rather than the next time you happen to look.

Check the first few drafts properly

Before trusting the pipeline, open the first two or three drafts and read them the way a buyer would.

You’re not checking whether the automation ran. You’re checking for the failure mode where everything ran correctly and the output is still wrong: right product, wrong orientation; good copy aimed at the wrong buyer; images in an order that buries the best one.

Those come from thin form input, not from broken scenarios, and they’re much cheaper to catch on draft three than on listing thirty.

Scan back over the modules once

When you’ve finished wiring, take one pass back across the scenario and confirm every module shows a connection and no warnings.

A little double-checking now saves a lot of debugging later — and debugging a chain of four scenarios is meaningfully harder than checking one of them before you start.

Nothing publishes without you

Worth repeating, because it’s the part that makes the whole approach safe: this creates drafts.

You keep the final read. You decide what goes live, at what price, and when. The automation removes the assembly work, not the judgement — which is the right division of labour, because assembly is what’s tedious and judgement is what sells.

What this costs to run

The blueprints are free. Running them requires Make.com’s cheapest paid tier, because the system needs four active scenarios and the free plan allows two. You’ll also need your own OpenAI API key, billed per listing.

If maintaining that stack isn’t appealing, Elistit does the same job from one sentence — images, print files, SEO copy, delivery, and a draft waiting in your shop. Same safety model: you still review and publish. There’s a free plan.

Where the files live

Every lesson, including all the install walkthroughs, is free and public on YouTube. The blueprints, templates and prompt library are in the free club.

Join free — no card, no approval queue.