Two workflows built and executed locally in n8n 2.42.5. These are self-created technical demonstrations with synthetic inputs. They are not customer projects, paid orders or production integrations.
01
CSV to declared value contract
Keep selected strings intact, require explicit column and empty-cell choices, then validate integer, decimal and text values against declared destination rules.
Manual trigger and synthetic CSV input
Explicit column choices and type declarations
CSV extraction and whole-batch validation
Selected rows and declared value checks
Native execution observed
Executed nodes
9
Result
2 rows, 8 values retained; database NOT_EXECUTED
Exact synthetic output strings and explicit NULL
SKU
Description
Price
Stock
00001
한글, quote "ok"
12.30
2
00002
NULL (declared blank policy)
0.00
-1
The demonstrated builder supports UTF-8/BOM CSV, 100 rows, 1–5 source columns and up to five selected typed columns. A signed integer accepting −1 does not validate a business stock rule. Live schemas, keys, collation, SQL modes, transactions and inserts remain unverified.
The draft total belongs to the separate three-row synthetic run. The existing ten-row review example below contains unresolved rows and therefore withholds the complete total.
The tested layout is RFQ-L1 text PDF, up to two pages and 20 items, with UTF-8 reference CSVs. Other PDF layouts, scans/OCR, customer Excel display, production n8n, ERP integration and final quote approval remain unverified. No quote was sent and no payment was made.
Agree the input format, selected fields, expected output, whole-batch stop conditions, review owner and one unseen acceptance example. Confirm the actual runtime, data-handling permission, feasible delivery date, revision scope and protected payment terms before starting customer work.
These examples do not establish production experience or promise arbitrary API/CRM integrations. A future service scope and price require agreement. There is no order form, automatic upload or new checkout on this page.
The summary contains synthetic outputs, node names, historical verification times and source hashes. It contains no credentials, customer data, runtime database, workflow source code or installation package. It does not execute a workflow.