n8n Workflow: Generate Valid GTIN-14 Test Values for Feeds

Generate format-valid GTIN-14 test values for your ecommerce feeds—automatically in n8n

This n8n workflow produces valid, format-validated GTIN-14 test values from a provided SKU prefix and quantity—then maps every generated value back to the prefix so you can reliably QA ecommerce feed formatting.

What this workflow does

• Receives input from the GTIN Form: quantity and a SKU prefix for each test request.
• Logs traceability by recording the raw form payload in the n8n run-log Data Table for the run.
• Validates and normalizes by bounding quantity (1–100) and trimming the SKU prefix before building an idempotent request.
• Generates GTIN-14 values by calling the Ecomwith GTIN Generator and formatting the returned GTIN-14 results.
• Maps for feed QA: each generated GTIN-14 is associated with its source SKU prefix so you can verify product-feed behavior end-to-end.
• Returns metadata or errors, including quota/rate-limit info, or a structured error object with troubleshooting links.

Use cases

• Feed QA automation: generate batches of GTIN-14 test values to validate formatting and mapping rules in your ecommerce data pipelines.
• SKU-to-identifier testing: confirm that SKU prefixes produce the expected GTIN-14 patterns in downstream systems.
• Regression testing: quickly re-run format validation when feed schemas, transformations, or validators change.

Technical details

• API authentication: create an Ecomwith API key with scope tools:gtin:generate and store it in an n8n HTTP Header Auth credential named Ecomwith API (header X-API-Key).
• Required n8n components: Code, Data Table (for the n8n-creator-run-log Data Table), Sticky Note, Form Trigger, and HTTP Request.
• Operational requirements: quantity 1–100 and a SKU prefix per request; verify the credential and run a smoke test before deploying.

Perfect for n8n users, automation engineers, and SaaS operators who need dependable GTIN-14 test data for ecommerce feed QA.