n8n automation

Automated Allegro listing optimisation: AI rewrites titles and descriptions

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.

Allegro REST API · OpenAI · Google Sheets · Gmail

In short

Automated Allegro listing optimisation is an n8n workflow that uses AI to rewrite offer titles and descriptions, working from data Allegro already holds: the offer’s parameters, its category and the fields that category requires. It’s built for sellers with dozens or hundreds of offers whose titles were written over the years, in a hurry and to different patterns. You choose in a sheet which offers to improve, and the workflow pulls their data through the Allegro API, generates a new version, checks it and writes it back. Before it changes anything, it backs up your offers, so the previous version is always to hand.

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

    Allegro listing optimisation: Offer backup → sheet queue → Allegro API data → AI writes title and description → validation → PATCH to Allegro → report

    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: Allegro listing optimisation with AI
    Workflow in n8n. Built by Bartłomiej Chwajoł.

    Sound familiar?

    What this solves

    Your titles were written over years, and no two follow the same pattern.

    AI writes titles to a single pattern, using the key attributes from the offer’s parameters: brand, model, size, material. Code enforces the character limit and rejects any version that goes over.

    Editing descriptions by hand means hours of clicking in the seller panel.

    The workflow processes offers in batches every hour without you. You tick in a sheet what to improve and review the finished changes in a report.

    You worry AI will break offers that sell well today.

    Before it starts, the workflow saves a backup of your offers to a sheet. Every new version is validated, and you switch on writing to Allegro per offer or per batch.

    How it works

    Step by step

    1. 01

      Offer backup

      A separate, manually started branch pages through your offers in the Allegro API, fetches full data for every offer not yet backed up and saves it to a sheet.

    2. 02

      A queue in the sheet

      Every hour the workflow reads the sheet and picks rows marked for improvement. A Limit node sets how many offers go through per run.

    3. 03

      Offer and category data

      For each offer it fetches the full content, the category and that category’s parameter list. A Code node turns it into a compact data package for the model.

    4. 04

      AI writes the title and description

      An LLM Chain with an OpenAI model writes the title and description to your guidelines. A Structured Output Parser returns them in a fixed format, ready for checks.

    5. 05

      Validation and description build

      Code checks the title length, required elements and banned phrases, then assembles the description into the section structure Allegro accepts.

    6. 06

      Saving to Allegro

      If the row is approved for saving, an HTTP Request sends the change to the Allegro API with PATCH. Without approval, the new version waits in the sheet as a proposal.

    7. 07

      Report and notification

      The sheet row gets a status, the new version and any error message. Gmail sends a summary of the run.

    Implementation details

    On Allegro, the Polish marketplace, the offer title does a lot of the selling: it’s how both shoppers and the site’s search work out what you’re offering. With a large catalogue, though, titles and descriptions get written in different years, by different people, to different rules. This workflow tidies them up in batches, without pausing sales or clicking through the seller panel.

    API data, not guesswork. The AI gets more than the current title: it also sees the offer’s parameters and the category’s parameter list, including required fields. So each new title is built from facts about the offer. The prompt explicitly tells the model not to add features that aren’t in the data, and validation rejects titles missing key elements such as brand or model.

    Safe changes. Before anything is overwritten, the backup branch saves full offer data to a sheet. A column in the sheet decides whether the workflow only prepares a proposal or writes it straight to Allegro. We usually start in proposal mode: you review the new titles, we refine the prompt, and you switch on saving for later batches once you’re happy with the results.

    Errors and limits. The workflow works in small batches to stay clear of API limits, and a single failure doesn’t stop the run. If Allegro rejects a change, say because of a disallowed element in the description or a title that’s too long, the reason goes into the sheet and the email report. We connect to the API with OAuth on your seller account, and the credentials sit in n8n’s encrypted store.

    The same approach works for new products: see automated product listing on WooCommerce, Allegro and Erli. If you also sell through your own store, read our WooCommerce vs Shopify comparison, and for the tool itself, what n8n is.

    01

    Integrations

    • n8n
    • Allegro REST API
    • OpenAI
    • Google Sheets
    • Gmail
    02

    What you need

    • An Allegro seller account and an app registered in Allegro’s developer portal (OAuth access)
    • A Google Sheet to act as the offer queue and hold the backup
    • An OpenAI API key (or another model provider) on your own account
    • Guidelines for titles and descriptions: pattern, tone, banned phrases, a few model offers
    • A mailbox for reports (Gmail or another)
    • An n8n instance on your server or in n8n Cloud
    03

    How we tailor it

    • Separate title patterns for different categories or brands
    • Titles only, descriptions only, or both
    • Rule-based selection of offers to improve, e.g. ones with no sales for a while
    • Approval of each change on Slack or Telegram instead of in the sheet
    • The same logic for other marketplaces or a WooCommerce store

    FAQ

    Frequently asked questions

    Could automatically changing titles hurt my offers?

    It can, if changes go out unchecked, which is why the workflow has a backup, validation and a proposal mode. It’s best to start with a smaller batch, compare sales against the previous period and only then widen the scope. We don’t promise uplifts: the title is one factor among many, alongside price, photos and reviews.

    Does Allegro allow editing offers through its API?

    Yes. Allegro offers sellers a REST API that covers reading and editing offers, categories and parameters. You need an app registered in its developer portal and authorisation for your seller account, which we set up during the project.

    What about descriptions that contain images?

    An Allegro description is made of sections containing text and images. The workflow can keep your existing images and replace only the text, or rebuild the sections from a template. We pick the approach during setup using examples of your offers.

    How many offers does each run handle?

    As many as you set in the Limit node. We tune the pace to your catalogue size, the API limits and how many changes you want to review. At the start people usually pick small batches so they can judge the quality calmly.

    Can I go back to the previous version of an offer?

    Yes. The backup sheet holds offer data from before the changes, so the previous title and description can be restored. If you like, we add a separate workflow that restores whichever offers you tick in the sheet.

    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 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.
    3. 03 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.
    4. 04 Multichannel product listing WooCommerce REST API · Allegro API · Erli API · OpenAI 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.
    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.