Conflict-Check Engine
A conflict check by eye misses the misspelling, the maiden name, and the LLC that dropped its suffix. Send this workflow a new party name and it fuzzy-matches every contact and matter you have, then emails you the possible matches to rule on. Free n8n workflow, yours to keep.
Import it into n8n
- The button above downloads the workflow as a .json file — that is the whole download.
- In n8n, open the workflows list, choose Import from File, and select the file you just downloaded.
- Open each node flagged with a warning and connect your own credentials — none of ours are in the file.
- Run it once manually before you activate it, and check the output is what you expect.
How it works
- Receives a conflict check request via a POST webhook, parses the submitted client/adverse party names, and rejects the request if no names are provided.
- Fetches up to 200 contacts and up to 200 matters from Clio using the configured base URL.
- Fuzzy-matches each submitted name against Clio contact names and matter client names/descriptions using a configurable threshold and flags whether any potential conflicts are found.
- Generates a unique conflict check ID, appends a pending-review audit row to a Google Sheets “conflict check” sheet, and builds a styled email report with decision links.
- Sends the conflict report email (and triggers a separate compliance/audit workflow), then responds to the original webhook with the check ID.
- Receives a conflict decision via a GET webhook from the email link, validates the check ID/action, updates the matching Google Sheets audit row with the decision and timestamp, and returns a confirmation or error page.
Compliance: never touches your legal work
This automation only handles operational steps — sending, routing, and moving data. It doesn’t draft, analyze, or make any legal judgment, consistent with ABA Opinion 512.
What’s inside
- The conflict-check workflowImport one JSON file. Post a name to it and a report comes back by email.
- Fuzzy matching, not exact searchCatches misspellings, entity suffixes, and name variants that an exact search walks past. You set the threshold.
- A decision you record, not one it makesThe report lists what matched and how closely. You click to record Cleared or Conflict, and it logs the result.
- 30-minute deploy guide + LoomConnect your case management, your sheet, and your email. No developer needed.
✓ Works great when
- Your contacts and matters live in Clio
- You want a documented check, not a quick search
- Your client list has outgrown what you can scan by eye
✗ What breaks at scale
- You need the check to fire automatically at intake
- Your archive runs past a few hundred contacts and matters
- Corporate families need checking, not just names
Frequently asked
What do I need to run this?
An n8n instance, Clio API access, a Google Sheets connection, and an email account. About thirty minutes.
Does it clear the conflict for me?
No, and it never will. It surfaces names that look similar and says how similar. Whether a match is a conflict is a legal judgment and it stays yours. The workflow records the call you make.
How many records does it check?
The free version reads up to 200 contacts and 200 matters, which covers a newer practice. Past that you are sampling rather than checking, and full-archive paging is a Build.
How do I set the match threshold?
It is a value you configure. Lower catches more variants and more noise. Higher is quieter and riskier. Tune it against names you already know are in there.
How does this compare to the Claude conflict checker?
Same job, different shape. This one runs against your live system on request. The skill runs on an exported list inside Claude Desktop with no integration. Pick whichever fits how you work.
Want the version built for your firm?
Done-for-You Build.
The free workflow runs a check when you ask, across your first few hundred records. When it should fire the moment a lead arrives, cover the whole archive, and follow corporate relationships, that is a Done-for-You Build. We wire it into your stack and hand it back tested.
What you get
- Conflict check fired automatically at intake
- Full-archive coverage with paging, not a first-page sample
- Related-party and corporate-family matching
- Results written back to the matter with the decision


