Skip to content
All projects

Insurance Agency · n8n Workflow Automation

Insurance — Lead Qualification and Renewal Automation

Portfolio Demonstration

A record-type Switch sends the item down one of two lanes with entirely different node sequences: new leads go through eligibility/completeness/agent-routing, while renewals go through expiration-date math, a Low/Medium/High risk score, and mandatory licensed-agent review - the lanes never share a node until the final log.

n8n canvas: Insurance — Lead Qualification and Renewal Automation — full workflow canvas in n8n

Problem

Agencies struggle to consistently qualify new leads and stay ahead of policy renewal deadlines.

System Design

Two-lane system: New Lead and Renewal are two long, visually separate horizontal lanes (one above, one below) that only touch at a shared final activity log.

Workflow Stages

  1. 01Lane A - New Lead Qualification
  2. 02Lane B - Policy Renewal
  3. 03Shared Activity Log

Tools Used

  • n8n
  • Code (JavaScript)
  • If
  • Manual Trigger
  • Set
  • Switch

Safety & Human Review

  • Workflow name begins with DEMO | and is inactive.
  • No credentials are attached to any node.
  • No enabled external send node exists anywhere in this workflow.
  • All data is fictional (example.com emails, invented names/addresses).
  • Uses only built-in n8n node types.

Implementation Evidence

Real screenshots of the working system — collapsed by default so this page stays readable.

What's Working

7 structural checks passed, including: Workflow JSON parses (local + server-returned copy); active is false; Name begins with DEMO |; No credentials attached to any node. Structural and logic validation completed. Live n8n execution pending manual safe test.

Limitations & Confidentiality

Classification and scoring logic is deterministic/rule-based rather than a live AI model, by design (provider-independent, fully inspectable, no credential required). No real system of record, messaging channel, or calendar is connected - every downstream action is simulated or drafted, never sent. Live n8n execution has not been triggered as part of this build.

Portfolio demonstration built for a fictional business with fictional data. It is not connected to any real client, system, or customer.

What I'd Improve Next

Replace deterministic classification with a real AI model behind the same confidence/human-review pattern where one exists. Connect the mock/simulated steps to real systems of record once reviewed and approved. Wire a real (approved) communication channel behind the draft-message steps.

Have a similar workflow to automate?

I'll tell you honestly whether automation is the right fix.