Interactive demo Processing rules Request path Operational limits Try demo → ← Back to overview
PIPELINE Inbound lead qualification →

Inbound leads verified in real time, without pipeline friction.

LeadIntel validates schema requirements, detects duplicate submissions, computes qualification scores, and routes accepted prospects through n8n.

01 / INTAKE Browser sends JSON payload
02 / VALIDATE FastAPI enforces schema
03 / SCORE Intelligent scoring with fallback
04 / ROUTE n8n dispatches audit logs

Every lead verified at intake. Zero duplicates in your database. Instant routing for qualified prospects.

Back to overview

Test the live intake engine.

Send a simulated enquiry to observe real-time schema validation, PostgreSQL persistence, and scoring. Use illustrative data only.

Lead intake LIVE ENDPOINT
All four fields are required. Submissions are processed by the live backend.
Illustrative sample data
✓
Submission result
No enquiry has been sent.
ID: Ready
Qualification score
— /100

A score will appear when returned by the backend.

Use fictional contact details in this demo.
Valid email format required; fictional addresses accepted.
Organisation or workspace name.
0 / 500
A concise description is sufficient. Do not include confidential data.
This is a working sandbox demo. Requests are validated by FastAPI, stored in PostgreSQL, and routed via n8n.
Pipeline execution Response time: Ready

One request, traceable lifecycle

01. Form and webhook n8n
The browser sends a same-origin JSON request to the intake webhook.
02. Validate and persist FastAPI
FastAPI validates fields, rejects duplicate source/external ID pairs, and writes the record.
03. Score intent FastAPI
An LLM evaluates intent; deterministic heuristics are used if LLM scoring is unavailable.
04. Qualify and route n8n
n8n applies the 70-point qualification threshold and records audit events.
Qualification rules Threshold ≥ 70
Manual review
Not qualified
Qualified
Awaiting submission ID: Ready

After the API returns HTTP 201, n8n executes qualification logic and writes the audit event.

Validation first. Routing second.

Responsibilities are cleanly separated: FastAPI manages intake verification and scoring, while n8n manages workflow branches and audit logs.

01 / VALIDATE

Strict schema validation

FastAPI requires name, valid email format, company, message, and source. Invalid requests return HTTP 422 before any lead is stored.

02 / DEDUPLICATE

Composite duplicate protection

A repeated source and external ID pair returns HTTP 409 Conflict instead of creating redundant records in PostgreSQL.

03 / SCORE

Resilient intent scoring

FastAPI uses LLM scoring when available, automatically falling back to deterministic heuristics if provider requests fail.

04 / DISPATCH

Deterministic qualification

n8n enforces the 70-point qualification threshold, records the event in audit tables, and triggers notifications accordingly.

Each system has one dedicated responsibility.

The actual request path implemented by this application—no simulated mock components.

Lead form
Collects intake fields
Caddy reverse proxy
Serves form & proxies webhook
n8n intake webhook
Forwards payload to FastAPI
FastAPI core
Validation & scoring
PostgreSQL
Persistent system of record
n8n qualification
Applies score threshold (70)
Audit event log
Traceable execution history
Notifications
Configured communication channels
Deterministic fallback activates automatically when LLM scoring is unavailable
Intake and scoring

FastAPI validates contracts, rejects duplicates, stores verified records in PostgreSQL, and produces the intelligence score.

Workflow and operations

n8n evaluates business rules, writes audit events, and dispatches downstream alerts. Downstream service outages do not affect intake acceptance.

The form confirms intake acceptance; downstream notifications execute asynchronously.

Production boundaries and operational expectations.

Working sandbox prototype

This public demo operates on cloud sandbox environments. Instances may sleep when idle and require a brief wake period on the initial request. Use synthetic information only.

Authenticated internal API

Internal FastAPI endpoints require valid Bearer token authorization, rejecting unauthenticated traffic with HTTP 401.

Predictable error semantics

Malformed submissions return HTTP 422 with field-level details. Duplicate submissions return HTTP 409 Conflict.

Scoring resilience

Leads receive scores even during provider outages through local fallback algorithms, ensuring intake never stalls.

Synthetic data notice

Submissions are stored in the demo PostgreSQL database for testing and demonstration purposes.

Sandbox demonstration

Inspect the live intake pipeline.

Submit an illustrative lead above to test schema validation, duplicate detection, and scoring in real time.

Open demo form →