How to Prepare Etsy Listing Data Automatically with Make.com

This is the scenario that does the thinking. Everything after it moves files around; this one turns a short form submission into the actual listing data — the title, the tags, the description, and the customer persona underneath all three.

It’s also the longest scenario in the chain, which is why it’s worth understanding rather than just importing.

Set up before you open Make

Two things need to exist first, or you’ll spend the build reconnecting modules.

The Drive folders. The collection folder, the shop-type folder inside it, and the product folders named by SKU. The scenario references these by path and doesn’t improvise when one is missing.

The data spreadsheet. One sheet for listing data, one for form responses, one for product templates. The scenario reads and writes across all three, and it expects the tabs to be there.

It also helps to work with four browser tabs open: Make, your Drive, the spreadsheet, and the form. You’ll move between them constantly, and hunting for windows is how you lose your place mid-wire.

Import, then save immediately

Import the blueprint, then hit save before touching anything.

A freshly imported scenario looks broken — modules with warnings, unresolvable fields, no account connections. That’s expected. Saving registers it so later scenarios can reference it, and gives you a stable point to work back from. Fix afterwards, not before.

Then get in the habit of saving again after every few modules. It costs a second and it means a mistake is never more than a few steps deep.

The first Sheets module

The scenario starts by reading your listing data.

Select the Google connection, approve the permissions if it’s the first time, then pick the spreadsheet — refreshing the dropdown before you choose. Then pick the sheet tab, refreshing again.

Both refreshes matter. Make caches these lists, and choosing from a stale list is the most common cause of “I selected the right sheet and it still fails.”

Leave the limit at 1

There’s a limit field on the read module. Leave it at one while you’re building.

It means each run processes a single product, which is exactly what you want while testing. You can raise it later once you trust the output, but debugging a run that processed twelve products is dramatically harder than debugging one that processed one.

Red dots while building are normal

You’ll see them constantly during the wire-up. A red dot means a module can’t complete as currently configured, which during a build usually means you haven’t got to it yet.

Save anyway, keep going, and come back. If a dot persists after the module is fully configured, then it’s worth investigating — and it’s still almost always a connection or a stale dropdown rather than anything structural.

The AI step, and what it’s actually reading

The generation step reads your form submission — the short description, the persona, the product type — and produces the listing copy from it.

This is where input quality shows up. The model isn’t inventing a product; it’s describing yours. A two-line description of what the thing is and who it’s for produces specific copy. A five-word description produces the bland output people blame the AI for.

The persona field does more work than its size suggests. The same artwork described for “new parents decorating a nursery” and for “students furnishing a first flat” produces genuinely different titles and tags, because it changes who the copy is talking to.

Cleaning the output to fit Etsy

Etsy has character limits, and AI output doesn’t respect them unless you make it.

The scenario trims and tidies the generated text so titles and tags fit rather than arriving truncated mid-word. It’s an unglamorous step that’s easy to skip when building your own version, and skipping it is why some automated listings have titles that stop halfway through a phrase.

The filter, and where the flow ends

Part way through there’s a filter controlling which path the workflow takes.

That choice decides where this part of the process finishes and which product type it’s treating the submission as. If you sell more than one kind of product, this is the branch point — you’d duplicate the downstream steps for each type rather than trying to make one path handle everything.

For a single product type, set it once and leave it.

Handing off to the next scenario

The last thing this scenario does is call the next one.

Modern Make handles this with a Scenario Call module rather than the old webhook-and-paste-a-URL approach. It’s worth knowing because a lot of existing tutorials still teach webhooks, and the two look nothing alike when you’re following along.

One practical note during setup: when a scenario is generating something you need for the next step, don’t close the window before it finishes. Closing early loses the state and you start that part again.

Test with one real product

Run it once, end to end, with a genuine product rather than placeholder text.

Check the sheet row that comes out: is the title one you’d actually publish? Do the tags describe the product or the category? Does the description sound like it was written for your buyer?

If any of those are weak, the fix is in the form input, not the scenario. That’s a useful thing to learn on product one rather than product twenty.

What this costs to run

The blueprints are free and yours to keep. Running them isn’t: four scenarios against Make’s two-scenario free plan means their cheapest paid tier, plus your own OpenAI key billed per listing. Roughly speaking the data step is the heaviest of the four in operations, because it’s the one doing the generation.

If you’d rather not run any of it, Elistit does this whole pipeline from a single sentence, with a free plan to try it on.

Where the files live

Every lesson 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.

Join free and take the lot.