n8n-nodes-lenz 0.1.5 → 0.1.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +20 -0
- package/dist/nodes/Lenz/Lenz.node.js +714 -842
- package/dist/nodes/Lenz/Lenz.node.js.map +1 -1
- package/dist/package.json +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +1 -1
- package/dist/credentials/LenzApi.credentials.d.ts +0 -12
- package/dist/nodes/Lenz/Lenz.node.d.ts +0 -5
- package/dist/nodes/Lenz/__tests__/Lenz.node.test.d.ts +0 -1
- package/dist/nodes/Lenz/__tests__/Lenz.node.test.js +0 -239
- package/dist/nodes/Lenz/__tests__/Lenz.node.test.js.map +0 -1
package/README.md
CHANGED
|
@@ -69,6 +69,23 @@ A simple "fact-check gate" pattern — verify an LLM's output before acting on i
|
|
|
69
69
|
|
|
70
70
|
For a lighter check on lower-stakes content, swap the Lenz operation to **Assess (Fast)** instead — same wiring, ~5-10s instead of ~90s.
|
|
71
71
|
|
|
72
|
+
### Follow-up questions on a completed verification
|
|
73
|
+
|
|
74
|
+
Ask a grounded question about the evidence behind a Verify (Deep) result, by chaining two Lenz nodes:
|
|
75
|
+
|
|
76
|
+
```
|
|
77
|
+
[Lenz node] ──▶ [Lenz node]
|
|
78
|
+
Operation: Operation:
|
|
79
|
+
Verify (Deep) Ask Follow-Up
|
|
80
|
+
Verification ID: {{ $json.verification_id }}
|
|
81
|
+
Question: "What are the main sources supporting this verdict?"
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
1. Add a **Lenz node**, set Operation to **Verify (Deep)**, and run it.
|
|
85
|
+
2. Add a second **Lenz node** after it, with Operation set to **Ask Follow-Up**.
|
|
86
|
+
3. Set the Verification ID field to an expression referencing the first node's output: `{{ $json.verification_id }}`.
|
|
87
|
+
4. Keep the Question field as a fixed string (e.g. `"What are the main sources supporting this verdict?"`) — it works for whatever claim was just verified, since only the Verification ID needs to change per run.
|
|
88
|
+
|
|
72
89
|
## Resources
|
|
73
90
|
|
|
74
91
|
* [n8n community nodes documentation](https://docs.n8n.io/integrations/#community-nodes)
|
|
@@ -80,3 +97,6 @@ For a lighter check on lower-stakes content, swap the Lenz operation to **Assess
|
|
|
80
97
|
* **0.1.0** — Initial release. Verify (Deep), Assess (Fast), Extract Claims, Ask Follow-Up, and Check Usage operations; API-key credential with live test endpoint.
|
|
81
98
|
* **0.1.1 - 0.1.3** — Publishing pipeline fixes (GitHub Actions provenance, npm trusted publishing).
|
|
82
99
|
* **0.1.4** — Bundled `lenz-io` at build time (zero runtime dependencies, required for n8n Cloud verification); added a Jest test suite; fixed an error-message bug in the `NodeApiError` wrapping; replaced the placeholder icon with the real Lenz brand mark.
|
|
100
|
+
* **0.1.5** — Corrected the maintainer email in `package.json` to match the npm account.
|
|
101
|
+
* **0.1.6** — Fixed every violation found by n8n's official `@n8n/scan-community-package` compliance scanner: test files no longer ship in the package; the bundled `lenz-io` SDK is properly tree-shaken (dropping unused webhook-signature-verification code); replaced remaining restricted-global usage (`setTimeout`, `process`, `console`, `globalThis`) with scanner-safe equivalents; and stopped emitting unused `.d.ts` declaration files. Also fixed a dormant bug in the npm publish workflow.
|
|
102
|
+
* **0.1.7** — Clarified the Verification ID field description and added an Ask Follow-Up wiring example to the README.
|