Zum Inhalt springen
NEUMarktplatz und trig8n Agent: Verkaufen Sie, was Sie bauen, und erhalten Sie Pläne und Änderungen, die getestet sind, bevor Sie sie sehen. Neuigkeiten ansehen

Bibliothek / Dateien & Cloud-Speicher

Dateien & Cloud-Speicher

Verkaufs-CSV-Uploads validieren und Freigabe-ZIPs mit n8n-Formularen erstellen

Durch einen Formular-Upload ausgelöst, validiert eine UTF-8-Verkaufs-CSV gegen zuvor freigegebene Chargen in der Data Table, lässt einen Prüfer sie genehmigen oder ablehnen und gibt ein Audit-ZIP zurück.

Was sie bewirkt

## Validate sales CSVs and generate review ZIPs with n8n forms Review recurring sales exports before a manual import. Upload one UTF-8 CSV, validate orders, compare them with previously released batches, and save an exact review. An authenticated reviewer can download, approve the accepted subset or reject it. Each result is returned as an audit ZIP. ### How it works Checks required columns, calendar dates, currency precision and duplicate groups. An n8n Data Table stores immutable batch snapshots and one authoritative release registry. Approval binds to the review hash and commits the release plus decision in one conditional update. Identical historical orders and conflicting IDs are excluded. No shop or accounting import is executed. ### Setup Run the separate setup utility once. Copy stateTableId and actual reviewer emails into both Configure nodes. Keep n8n User Auth and Include User in Output enabled on both forms. Run the credential-free demo, then upload examples/sample.csv with a unique batch ID. Copy batch_id and review_hash from report.json into the decision form. Approve requires typing RELEASE ACCEPTED ROWS. ### Requirements and limits Tested on n8n 2.28.6; Data Tables and n8n-user Forms required. Built-in nodes; no service credentials for this workflow. Required headers: order_id,order_date,amount,currency. One order per row, max 1,000 rows per upload. Run one intake at a time. Registry limits: 5,000 released orders, 1,000 decisions, 4,000,000 serialized characters. Decisions expire after 24 hours by default. Re-upload with a new batch ID if release history changes. Customize limits only with tests.

Die Schritte

  1. Upload sales CSV for review
  2. Configure intake and authenticate
  3. Read uploaded CSV
  4. Parse CSV and check headers
  5. Validate sale fields
  6. Resolve duplicate order IDs
  7. Build review files
  8. Read canonical validation report
  9. Read release registry for intake
  10. Read history and preserve input
  11. Check unique batch ID
  12. Build immutable history-aware review
  13. Save immutable batch snapshot
  14. Verify saved review

Insgesamt 30 Schritte.

Ähnliche Automatisierungen