Stockwell Commerce was building Typeform surveys by hand for every new product. With hundreds of SKUs and no end in sight, the CS team was buried in mechanical work. We automated the entire pipeline from Google Sheets to published form link — in under 4 seconds per product.
Stockwell Commerce runs a large and continuously expanding product catalogue. For every new product, their Customer Service team was manually duplicating a master Typeform template, personalising it for the product, generating the link, and logging it in their tracking sheet. With new products being added constantly, this had become a significant and recurring drain on a team that should have been focused on customers.
The work was entirely mechanical. There were no judgment calls in the process — just template duplication, field replacement, and link logging. Work that should have been owned by a system from the start. They came to Soch to fix it, and we built a pipeline that removed every manual step in the chain.
Every new product required four to six manual actions from the CS team. There was no error handling — if a step was missed, no one knew until a customer hit a broken link. The team had no reliable way to see which products had forms and which did not without manually checking the sheet.
We were spending hours every week on this. It was one of those tasks nobody questioned until someone actually looked at it. Now it just happens and the CS team does not think about it at all.
We worked with the CS team to trace every step in the Typeform creation process, documented the personalisation logic for each product type, and identified which fields needed dynamic replacement versus which could remain templated. This gave us a precise spec before we wrote a single line of workflow logic.
We built an n8n workflow triggered by a Google Sheets row update. The pipeline retrieves the master template via Typeform's GET endpoint, runs product-specific personalisation through a custom JavaScript node, creates the new form via the Typeform API, and writes the finalised link back to the correct row in the tracking sheet. The workflow processes 204 items per cycle with clean conditional routing and no manual involvement.
We built execution logging with timestamps, per-run success and failure status, and error flagging for any products that could not be processed. The CS team now has a full audit trail and clear visibility into the pipeline's health — without managing any of it manually.
Per product form created. The entire pipeline runs faster than the old first step alone.
Items processed per execution cycle. The catalogue can scale without the team scaling with it.
Consistent form configuration. Every form is built from the same template with the correct product data applied automatically.
