n8n automation

Automated product listing on WooCommerce, Allegro and Erli

You enter the product data once, and an n8n workflow picks the category on each platform, writes the copy, prepares the images and creates the product in WooCommerce plus offers on Allegro and Erli. At the end you get one record with the result from every channel.

WooCommerce REST API · Allegro API · Erli API · OpenAI

In short

Automated product listing on WooCommerce, Allegro and Erli is an n8n workflow that turns a single product submission into three ready listings: a product in your own store and offers on two Polish marketplaces. The data arrives through a webhook, for example from a form, a sheet or your inventory system, and the workflow fetches each platform’s categories and required attributes, uses AI to pick the category, writes the copy and prepares the images. It’s built for stores selling across several channels that today type the same product in three times, in three different panels. Each channel gets the data in its own format, and you get one record with the outcome.

Workflow

This is the workflow in n8n

A simplified, interactive version of our workflow. Drag the nodes and run it to watch the data flow.

Drag the nodes · click “Run”

Execution log

    Product → 3 channels: Product webhook → platform categories → AI picks the category and writes the copy → images → WooCommerce, Erli and Allegro

    Screenshot from the build

    The full workflow in our n8n

    A real, unedited screenshot from the n8n editor. The interactive version above is simplified; here you can see every node, branch and error path.

    Full size
    n8n workflow: Multichannel product listing
    Workflow in n8n. Built by Bartłomiej Chwajoł.

    Sound familiar?

    What this solves

    You enter the same product three times, in three panels.

    You provide the data once. The workflow normalises it into a shared format, then maps it separately onto WooCommerce, Allegro and Erli fields, including variations in your store.

    Every platform has different categories and different required fields.

    The workflow pulls categories and attributes from each platform and builds maps from them, and AI picks the best-fitting category. Before anything is listed, validation checks that every required field is there.

    Copy and photos are missing, so new products sit waiting to be listed.

    A language model writes the name, description and attributes, and an image model prepares front and back shots, including from a reference photo. If the images fail the check, the product goes no further.

    How it works

    Step by step

    1. 01

      Product submission

      The data hits a webhook, code parses it and the sender gets an immediate “accepted” response. Everything else happens in the background.

    2. 02

      Categories and attributes from each platform

      The workflow fetches categories and attributes from WooCommerce, Erli and Allegro in parallel and builds the maps the AI works from.

    3. 03

      AI picks the category

      The model matches the product to a category on each platform. Validation checks the required fields, and an incomplete product stops with a list of what’s missing.

    4. 04

      Product copy

      The data is normalised, and an LLM with an output parser writes the name, description and attributes in a fixed format that every channel draws on.

    5. 05

      Product images

      The workflow builds a prompt, checks for a reference photo and generates front and back shots. The images are gathered and checked before the product moves on.

    6. 06

      Publishing to three channels

      A router sends the product to WooCommerce with its variations, and the offers to Erli and Allegro, each in that platform’s format.

    7. 07

      Final record

      Results from every channel (IDs, links, errors) are collected into one record that goes to your system or sheet. A separate webhook lets you regenerate just the images.

    Implementation details

    Selling across several channels makes sense until adding a product starts taking longer than selling it. Every platform has its own category tree, its own required parameters and its own description format. This workflow takes over the job of translating one product into three formats, and all you supply is the source data.

    Categories from real lists. The workflow fetches current categories and attributes from the platforms and builds maps from them. AI chooses a category from a list that actually exists, so it can’t invent names. Validation then checks the required fields for the chosen category. If something is missing, such as material or size, the product goes to no channel at all and the record lists the gaps.

    Copy and images under control. The language model works with an output parser, so it returns the name, description and attributes in a fixed structure. Images are generated from a prompt built on the product data, and when you have a reference photo the model uses it as the starting point. A listing photo should show the actual product faithfully, so during setup we agree when the workflow generates shots and when it sticks to your own photos. If a result misses, a separate webhook regenerates the images without relisting the product from scratch.

    Every channel’s result in one place. At the end the workflow gathers the responses from WooCommerce, Erli and Allegro: IDs, links or error messages. If one channel rejects an offer, the others aren’t held up, and the record shows exactly where the data needs fixing. To begin with, you can also list products as drafts where the platform allows it and review them before they go live.

    Once your offers are live on Allegro, you can refine them with automated Allegro listing optimisation, and translate your store with AI WooCommerce product translation. Still choosing a platform? Read our WooCommerce vs Shopify comparison or see how we build online stores.

    01

    Integrations

    • n8n
    • WooCommerce REST API
    • Allegro REST API
    • Erli API
    • OpenAI
    • Image generation API
    02

    What you need

    • A WooCommerce store with REST API keys for reading and writing
    • An Allegro seller account with an app in Allegro’s developer portal
    • An Erli seller account with API access
    • A product data source that can send a webhook: a form, a sheet, an inventory system or a PIM
    • API keys for a language model and an image model on your own account
    • Agreed prices, stock levels, shipping rates and return terms for each channel
    03

    How we tailor it

    • Only some of the channels, or extra ones such as another marketplace with an API
    • Your own photos instead of generated ones, or background clean-up only
    • Approval of copy and images before publishing
    • Different prices, names and descriptions per channel
    • Listing as a draft or inactive offer for a manual check

    FAQ

    Frequently asked questions

    Do my products need to live in a particular system?

    No. All you need is a source that can send data to a webhook: a form, a sheet with a button, an inventory system or a PIM. We agree a shared data format, and the workflow maps it onto each platform.

    What if the AI picks the wrong category?

    The AI can only choose from categories fetched from the platform, and validation checks the required fields. During setup we test the matching on your range and add fixed rules for product groups where the category is obvious. You can also switch on approval before publishing.

    Can AI-generated photos go into listings?

    A listing photo should show the product you’re actually selling, so generation makes most sense when the model works from your reference photo. During setup we agree when the workflow creates shots and when it only uses your own photos.

    What about variations such as sizes and colours?

    In WooCommerce the workflow creates the product together with its variations. Marketplaces handle variants differently, so we fit that part to Allegro’s and Erli’s rules during setup, using examples from your range.

    Does the workflow also sync stock and prices?

    This workflow lists new products. We build stock and price sync between channels as a separate automation, because it runs on a different rhythm and carries different risks.

    Get a quote

    Want this in your business? Tell us what it should do.

    Describe your process and the tools you use. We reply within one business day with an implementation plan.

    What do you need?

    Goal, deadline, links to inspiration — the more specifics, the more accurate the quote.

    Other builds

    More n8n automations

    1. 01 AI songs for YouTube OpenRouter · fal.ai · YouTube Data API · Telegram An n8n workflow takes an idea from the queue, writes the lyrics, generates a song with vocals, cover art and a video, then sends you a preview on Telegram. Nothing reaches YouTube until you approve it.
    2. 02 Allegro listing optimisation with AI Allegro REST API · OpenAI · Google Sheets · Gmail Every hour, an n8n workflow takes the next offers from a sheet, pulls their data and category parameters from the Allegro API, and AI writes a new title and description. Changes reach Allegro only after validation, and every offer is backed up first.
    3. 03 AI email assistant on Telegram IMAP · OpenAI · Telegram Bot API · SMTP An n8n workflow reads your inbox, filters out spam and sends the emails that matter to Telegram. You record a voice note with your answer, AI turns it into a finished email, and one button sends, revises or discards it.
    4. 04 AI-personalised email & SMS n8n · OpenAI / OpenRouter · Google Sheets · SMS gateway An n8n workflow pulls contacts from a Google Sheet, writes each person their own message, sends the email and, for mobile numbers, an SMS too. The sheet shows you straight away what went out and what was delivered.
    5. 05 AI WooCommerce product translation WooCommerce · WordPress REST API · OpenAI · Google Sheets An n8n workflow takes untranslated products from a queue, and AI translates their titles, descriptions, attributes and SEO meta into the languages you choose. Each result is checked for completeness and length before it reaches your store.
    6. 06 AI SEO landing pages for WordPress Google Search Console · OpenRouter · WordPress REST API · Google Sheets An n8n workflow takes a keyword from a sheet, analyses the search results, plans the structure and writes a landing page with links to your existing pages. The finished page lands in WordPress as a draft for you to approve.