Litigation risk check for new HubSpot companies

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.