n8n Automation Pipelines
Turn repetitive catalogue work into connected workflows.
The business problem
Manual product entry and disconnected catalogue tools made commercial operations repetitive and difficult to keep consistent.
My contribution
My role covered workflow definition, architecture, direction of AI-assisted implementation, service integration, testing and deployment. Platform and library authorship belongs to the third parties credited below; additional collaborators are not identified in the public project notes.
n8n is an existing orchestration platform; the contribution is workflow design and commerce integration.
Architecture & boundaries
n8n connects product creation with the Upgates API and Python data preparation. The wider migration toolkit uses Playwright, Czech/Slovak normalisation, progress files and valid EAN-13 generation.
- 01Product inputStructured catalogue data
- 02Validate & transformPython / workflow steps
- 03API integrationCommerce-platform write and review
Labelled architecture overview, reconstructed from project documentation. This is not a production trace.
Failure paths & design decisions
A migration total can be mistaken for workflow throughput.
Keep the 314-SKU migration scope separate from n8n execution metrics.
Evidence boundary: No execution-count or time-saving claim is made.
Delivery record
- Status
- Commerce workflow automation described in the project records.
- Users & scope
- Product creation and catalogue operations. Records refer to both Upgates and PrestaShop workflows; those integrations are separate.
- Dates & usage
- Workflow delivery dates and run volumes are not published.
Results & measurement gaps
New product creation runs through a single n8n workflow. The associated catalogue migration covered 314 SKUs; that migration figure is context, not a separate n8n throughput claim.
No public workflow export, success-rate history or run-time benchmark is available.