Problem

Answer incoming questions only from a controlled knowledge base (synthetic clinic information and safety rules), never invent missing facts, and hand the request to a person when the documents do not cover it.

My role

Author: designed, built and live-tested the workflow.

Technologies

n8n · webhook · knowledge-base retrieval · local language model · safety rules

Solution

A message arrives through a webhook. The workflow retrieves relevant knowledge-base entries and safety rules, then decides whether the request can be answered. A supported question gets a concise answer with a validated citation. If the documents contain no answer, nothing is invented and the request is routed to a person. Emergency wording is handled before generation: the model is skipped and the reply points to emergency services.

How it was checked

Three paths were live-tested in n8n with a local language model: a supported cleaning question, a question the documents cannot answer (implant price) and an emergency message.

Confirmed result

The cleaning question returned a concise answer with a validated knowledge-base citation. The documents contain no implant price, so none was invented and the request went to a person. The emergency message skipped the model and pointed to emergency services.

Materials: demo video with EN / DE / UA subtitles · transcript (WebVTT) (opens in a new tab)

Problem

Pass an incoming lead on in a controlled way: validate it before any downstream action, enrich it, derive a priority, create a clean CRM record and notify a second system.

My role

Author: designed, built and live-tested the workflow.

Technologies

n8n · webhook · REST API calls (enrichment, CRM, notification) · JSON

Solution

A lead arrives through a webhook and is validated before anything else happens. The workflow calls an enrichment API, derives the lead priority, builds a clean CRM record and sends a structured notification payload to a second endpoint.

How it was checked

Live test in n8n with a fictional lead. The retained evidence contains only fictional data and sanitized responses.

Confirmed result

All three API calls completed successfully and n8n returned HTTP 200.

Materials: demo video with EN / DE / UA subtitles · transcript (WebVTT) (opens in a new tab)

Problem

A workflow processing orders failed with HTTP 500 whenever the payload lacked a nested customer email. Root cause: it assumed every payload contains one.

My role

Author: diagnosed the failure, implemented the fix and re-tested it.

Technologies

n8n · webhook · JSON validation · HTTP responses

Solution

Safe field access, email validation, item validation and explicit rejection responses replace the unchecked assumption.

How it was checked

The same malformed input was replayed against the corrected workflow, followed by a second test with two valid line items. The failed execution and both fixed executions are retained as evidence.

Confirmed result

For the malformed input the corrected workflow returns HTTP 200 and explains that the email is invalid. The second test processed two valid line items and calculated a total of 211 euro.

Materials: demo video with EN / DE / UA subtitles · transcript (WebVTT) (opens in a new tab)