Authority Reached Where the Work Is Happening
This connector is not prebuilt. It would be built to your requirement, reached from a workflow over HTTP, with scope and effort agreed per engagement. Westlaw is the legal research service most firms and government legal departments already subscribe to, covering case law, statutes and secondary sources. Reaching it from inside a workflow means a question needing authority is answered as a step, rather than by someone searching separately and pasting a citation back.
How it connects
There is no dedicated Westlaw node. The HTTP Request node would call Westlaw as a step in a workflow, with its settings fixed at design time, and an IF or Switch node would route to it only the runs that need authority. What an engagement settles first is licensing rather than plumbing: a Westlaw subscription governs who may access what and how results may be used, so the terms of the organization's own agreement decide what a workflow is permitted to do with a result. That is a contract question, and it belongs at the start.
The credential the connection carries would be the boundary on the Westlaw side, so what a workflow could reach is what that subscription and that credential allow. Where an answer also draws on the organization's own material, retrieval from the library runs under the asking user's identity with their access list pre-filtered, so internal material stays scoped to the person asking even when the authority is shared.
Westlaw stays the research service and the authority stays there. Nothing would be copied into the library unless a step is scoped to retain a result, and whether that is permitted is part of the same licensing question.
What you can do together
- Answer a question that needs authority as a step in the matter's workflow, so the citation belongs to the record.
- Ask across published authority and the matter's own documents and recordings at once, each source cited.
- Reach for authority only on the branch of a workflow that needs it, rather than on every run.
- Keep internal material scoped to the person asking, while the authority half is shared.
A scenario
- ScopingThe engagement would establish what the subscription permits, which credential is used, and whether results may be retained.
- SetupAn HTTP Request node would be configured within the matter workflow under that credential.
- A questionCounsel would ask how an argument has been treated, and the workflow would reach Westlaw for the authority.
- One answerThe response would cite the authority beside the interview transcript the argument turns on, the internal half scoped to counsel's own access.
- The recordThe lookup would be part of the workflow run, so the research behind an advice note would be reproducible.
What stays where
Westlaw remains the research service
Case law, statutes and secondary sources stay there, and the citation points at the authoritative text.
Licensing decides what is permitted
What a workflow may do with a result, including whether it may be retained, follows the organization's own subscription terms.
The credential would be the boundary on the Westlaw side
What a workflow could reach is what the subscription and credential allow.
Processing runs where you deploy the platform
Reaching Westlaw needs an outbound network path, which an air-gapped deployment does not have.
Products and solutions
Next step
See it on your own Thomson Reuters Westlaw instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/thomson-reuters-westlaw