How to Build an n8n AI Agent for Legal Intake and Document Triage

A prospective client fills out a contact form describing their situation, and before an attorney can do anything with it, someone has to read it, figure out which practice area it falls under, check for a conflict of interest, and gather the 4 or 5 basic facts a first call will actually need. Wire an n8n AI agent into that intake, and it can do the sorting and gathering, strictly stopping at the line where anything resembling legal judgment begins.

What can the agent actually do during intake?#

Collect facts, not judgments: what happened, when, who was involved, what documents already exist, and what outcome the person is hoping to achieve, all stated plainly and recorded without the agent interpreting, weighing, or evaluating any of it any further than that.

Sort the inquiry into a practice area, family, personal injury, estate, business, based on the facts stated, and check the named parties against your firm's existing client and matter list for an obvious conflict before anyone on staff spends time on a call.

Write the practice-area categories as concrete fact patterns the agent can match against, the same discipline as routing a support ticket or a maintenance request elsewhere in this series: "mentions divorce, custody, or separation" maps to family law; "mentions an injury from an accident" maps to personal injury. A vague "sounds like it could be several things" case should route to an attorney to sort, not the agent guessing.

Statute-of-limitations urgency is worth flagging as a fact, not evaluating as a deadline. If the inquiry mentions dates that suggest a filing window might be closing soon, flag that timing explicitly for immediate attorney attention rather than calculating whether it is actually still open; that calculation itself is a legal judgment the agent should never make.

Facts gathered and sorted, never a judgment formed.

How does a conflict check actually work here?#

Match the names the prospective client mentions, themselves, the other party, any company involved, against your firm's existing client and matter records. A match does not mean the agent decides there is a conflict; it means the inquiry gets flagged for an attorney to make that determination before any further contact happens.

A name that partially matches, a common name, a similar but not identical company name, should flag for a human to check rather than the agent silently deciding it is not a real match. A missed conflict is a serious problem; a flagged non-issue costs someone 2 minutes.

Keep the conflict-check data itself narrowly scoped and access-controlled. The agent needs enough of your client and matter list to compare names against, not full case files or privileged content, and the workflow's credentials should reflect that boundary directly rather than relying on the agent's instructions alone to respect it.

A flagged match is not the same as a confirmed conflict.

What should the agent tell the prospective client?#

Confirm what was received and what happens next, nothing at all about their situation's merits or likely outcome. "Thank you, this has been routed to our family law team, someone will contact you within 1 business day" is a safe, useful confirmation.

"It sounds like you have a strong case" or "that's likely a violation of your rights" is legal analysis, and it is exactly the line this agent must never cross, no matter how confident or reasonable the answer might sound in the moment.

If a prospective client asks a direct legal question during intake, "do I have a case," "what should I do," the agent's only correct answer is that an attorney will address that on the call, not an attempt to be helpful with a partial answer. A partial legal answer from an unqualified source is often worse than no answer at all.

Write the deflection consistently rather than leaving the wording to vary by request. A single, tested response, "an attorney will go over that with you on your call, I can't offer legal advice," used every time a legal question comes up in intake is more reliable than trusting the model to phrase an appropriate deflection fresh each time.

Every step stops short of anything resembling legal judgment.

How does document gathering fit into intake?#

Ask for documents the person is likely to already have, not documents that require them to go find something first: a copy of a contract, photos of an incident, prior correspondence, a police report number if one exists. List what to request as a category-specific checklist, since a personal injury intake and a business dispute intake need genuinely different documents.

Route uploaded documents into your case management system by category and matter, tagged with what the prospective client said each one is, so an attorney's first look at the file is organized instead of starting from a folder of unsorted attachments with no context for what they are.

Never let the agent interpret a document's contents beyond basic categorization. Filing a document as "appears to be a lease agreement" based on its title and format is reasonable; summarizing what a contract's termination clause means for the client's situation is legal analysis, and the agent has no business generating that summary even as a courtesy.

A tested, consistent line is safer than a fresh answer every time.

What breaks, and how do you debug it?#

The most common failure is a fact pattern that touches 2 practice areas at once, an injury that happened during a business dispute, a divorce with a business asset involved, and forcing it into a single category loses information the routing was supposed to preserve.

Let the agent flag multiple categories rather than picking one when the facts genuinely span more than one area of practice.

Turn on Return Intermediate Steps on the AI Agent node and review exactly which facts drove the category and conflict-check decision before assuming the routing logic itself is broken.

Audit a sample of 10 or so intakes each month against what an attorney would have concluded from the same facts; the general agent-not-working checklist covers connection issues, but a wrong category here is more often a fact pattern the routing rules never anticipated.

Is this worth building for a small firm?#

Build it when inquiry volume is high enough that intake triage is genuinely eating attorney or paralegal time that could go toward billable work, a firm getting a steady stream of contact-form inquiries across multiple practice areas. A solo practitioner getting a handful of inquiries a week can likely read each one directly just as fast.

The honest value is speed and consistency on the sorting and gathering, never a substitute for the judgment only a licensed attorney can provide. Every inquiry gets the same conflict check and the same fact-gathering, every time, and the attorney's first call starts from an organized intake instead of a blank slate, with the line between gathering facts and practicing law held firmly throughout.

Every path stops at gathering and flagging; the attorney makes every real decision.