Litigation risk check for new HubSpot companies

Every time a new company is added to HubSpot, run a public-record litigation check and drop a one-paragraph risk read on the record as a note.

Agentic Task
HubSpotCourtListenerSalesOperationsLead EnrichmentResearch & Monitoring
PromptCreate

Build an agent workflow that runs a public-record litigation due-diligence check on every brand new HubSpot company so my AEs walk into the first call already informed.

Trigger: HubSpot webhook for newly created companies. When the webhook fires, the agent should pull the new company's id and current properties (at minimum its name and domain) using HubSpot Get Company before doing anything else, so it is working from the live record and not just the webhook payload.

Then the agent should run a CourtListener litigation check:

1) Use CourtListener Search across both dockets and opinions for the company's legal name plus a small set of likely aliases derived from the domain and the registered name (for example strip Inc, LLC, Corp, Holdings; add and drop common abbreviations; expand domain stems into plausible brand variants). Scope to the last five years by filtering on filing or decision date. The agent should reason about which aliases are actually worth searching rather than firing every permutation.

2) For the most relevant hits (typically the top three to five that actually look like the same entity), call CourtListener Get Docket and CourtListener List Docket Entries to pull case posture and the most recent filing so the read reflects what is live, not just what is on file.

3) Synthesize a single paragraph risk read covering: how many active cases the company is currently involved in, the dominant nature of suit codes that show up (employment, contract, IP, securities, etc.), whether the company is most often plaintiff or defendant, and any notable recent activity in the last ninety days. Be explicit about uncertainty: if multiple entities share the name and the agent cannot confidently match them, say so in the note rather than guessing.

Finally, drop the read back onto the HubSpot company record using HubSpot Create Note, associated to the company. The note body should start with a clear "Litigation Risk" label, contain the one paragraph summary, and end with a link to the CourtListener search URL used so the rep can click through and dig further. If there are zero credible hits, still write a note that says so plainly, so the absence of risk is logged too.

Make it agent-shaped, not a fixed pipeline. The alias generation, the judgment of which search results actually correspond to this company, and the tone of the risk summary all require reasoning rather than rigid rules.

Additional information

What does this prompt do?
  • Watches HubSpot for newly created companies and kicks off automatically the moment one lands.
  • Searches U.S. federal and state court records on CourtListener for the company's legal name and likely aliases derived from its domain, scoped to the last five years.
  • Pulls case posture and recent filings on the top matching cases so the read reflects what is actually live, not just what is on file.
  • Writes a one-paragraph litigation summary back to the HubSpot company record as a note labeled Litigation Risk, with a link to the underlying search so the rep can dig deeper.
What do I need to use this?
  • A HubSpot account with permission to receive webhooks for new companies and to add notes on company records.
  • A free CourtListener account so we can search U.S. court dockets and opinions on your behalf.
  • An idea of which company name field on the HubSpot record to trust (legal name versus brand name) if your team uses both.
How can I customize it?
  • Change the time window (the default is the last five years) if your team only cares about very recent activity, or remove it to surface historical patterns too.
  • Narrow the search to specific case types or jurisdictions, for example only federal courts or only employment and securities matters.
  • Tweak what the note actually says: add a risk tier (low, medium, high), include the top three case names with links, or route high-risk hits into a Slack channel for review.

Frequently asked questions

Does this replace a real legal due-diligence review?
No. This is a fast first pass built on public court records so your reps walk into the first call informed. Real due diligence still belongs with counsel.
What if the company has a common name and the search returns matches that are not really them?
The agent reasons about which results look like the same entity using the domain, location, and case context, and it calls out uncertainty in the note rather than guessing. You can also tighten the search to a specific jurisdiction or case type.
Will it cover state courts too, or only federal?
CourtListener covers more than three thousand federal and state courts, so the search hits both. You can scope it down to federal only if you prefer.
Does this work for companies created in HubSpot Free?
Yes, as long as your HubSpot plan supports company webhooks and you can add notes to company records. Most plans do.
Where does the litigation summary actually end up?
As a note pinned to the HubSpot company record, labeled Litigation Risk, with a link out to the full CourtListener search so anyone on the deal can click through.

Stop sending AEs into discovery calls blind.

Connect HubSpot and CourtListener once, and every new company gets a litigation risk read on the record before the first call.