Portfolio demonstration · n8n · Gemini · Groq

A fictional lead-to-cash scenario showing how disconnected sales handoffs can be organized with AI-assisted drafting, human decisions and recorded finance controls.

The challenge

Leads, proposals, reviews, contract and invoice records, and payments often move across separate tools. This demonstration explores a structured handoff and an auditable state trail; it does not claim measured client results.

How it works

Six modular n8n workflows and eight Data Tables support the flow:

  1. A form captures and normalizes a lead; email lookup checks for duplicates.
  2. Gemini qualifies the lead with Groq fallback. Validated output updates the CRM; failures are recorded.
  3. An AI-assisted proposal and illustrative quote are drafted and stored.
  4. A human sales reviewer approves or rejects the proposal; decisions are logged.
  5. Contract and invoice records are drafted. A finance reviewer controls release.
  6. Manually entered receipts feed balance checks, revenue summaries and a private dashboard.

Updated main workflow diagram generated from corrected JSON

Updated main workflow diagram generated from corrected JSON

The diagram is generated from corrected workflow JSON, not a live execution screenshot. Original editor screenshots predate the structural QA changes.

Walkthrough and evidence

Watch the 67-second English demo · English captions

The video is an edited screenshot-based montage, not a live screen recording.

The supplied local JavaScript simulator passed 39/39 scenarios and visited 157/157 executable nodes. It uses mocked n8n internals and synthetic model responses; it is not a live n8n, Gemini, Groq or financial integration test. Read the QA report.

Boundaries and tailoring

This is a portfolio demonstration, not a production deployment. Payments are manually logged, with no bank settlement or reconciliation; signature evidence is human-declared, not independently verified. No completed payment gateway, customer ROI or production readiness is claimed. The public exports need credentials, subworkflow and Data Table connections restored and fresh runtime testing.