CRM lead enrichment pipeline
A sub-workflow any collector can call. It maps the incoming lead to the CRM's shape, asks Claude for a short executive problem statement, assembles the record and fires it at GoHighLevel. Reps open the CRM and the research is already done.
- Trigger
- called by the monitor
- Time per lead
- about 3 s
- Manual entry
- none
- Output
- contact and opportunity in GoHighLevel
Why it exists
Reps spend hours researching a company before a call and then write inconsistent notes. Everyone captures something different and leadership can't see a clean pipeline.
How it runs
Receive
The intelligence monitor calls this workflow after a company is scored, with the full lead package.
Map
A code node reshapes the data into GoHighLevel's format: contact fields, company fields, custom attributes.
Write the problem
Claude gets the company context and the signal and writes a two or three sentence problem statement. Specific, no filler.
Assemble
The record is built up: company, decision maker, the problem, urgency score, the evidence and a suggested next step.
Push
The payload goes to GoHighLevel by webhook. Contact and opportunity are created or updated.
What came out of it
Reps open a lead and the research is there in plain words. Every record has the same fields, so the pipeline view finally means something.
Notes
Keeping this as its own sub-workflow means any collector can feed it, not just the monitor. If the CRM changes, only this one workflow changes.
This pattern is now part of the buyer intent research pipeline.
Stack
- n8n
- Claude API
- GoHighLevel
- Webhooks
- JavaScript code nodes
Want something like this built?
Tell me what you're trying to automate. Most things can be built in a week or two.