Jev n8n node (TypeSafe AI): official vs community nodes, and what each does when the Jev call fails
"jev n8n" was offered as a search suggestion by Google and by YouTube on ; Google also offered "jev n8n github". A suggestion shows that people search for the phrase, not how many do. Several n8n nodes for Jev are on npm, and two of them share the name n8n-nodes-typesafe-ai. This page shows which one TypeSafe publishes, which one runs on n8n Cloud, and what five nodes, read in source, do to your workflow when the Jev call fails.
Only the scoped @typesafe-ai/n8n-nodes-typesafe-ai is TypeSafe's (npm provenance, n8n-verified); the unscoped n8n-nodes-typesafe-ai is a third party's. All 5 nodes read stop the workflow on a Jev error by default.
With Continue On Fail on, 3 of the 5 can send a failed item down a real branch unless a fallback output is set. The five are the official node and four community nodes picked from 15 Jev and TypeSafe n8n packages found on npm, preferring packages with a public repository (see how the five were chosen). Not a survey. The pool installed none of them and ran no workflow.
Which one to install
Both packages below use the name n8n-nodes-typesafe-ai. The only difference in the name is the @typesafe-ai/ scope in front. The npm records show who publishes each. Documented npm registry records and SLSA attestations, read 3 Oct 2026, 05:20–05:21 UTC; maintainer lists re-read 05:27 UTC
TypeSafe's node: install this one
@typesafe-ai/n8n-nodes-typesafe-ai
- Version
- 0.9.0, published (the only version)
- npm maintainers
alliesafeanddiogo149, both with typesafe.ai email addresses- Repository field
typesafe-ai/n8n-nodes-typesafe-ai- SLSA provenance
- Yes: built from
github.com/typesafe-ai/n8n-nodes-typesafe-ai,refs/tags/0.9.0, commitc12537b - n8n's community-node listing
- Listed,
isOfficialNode: true, company "Typesafe AI", since - On n8n Cloud
- Yes (verified)
A third party's node with the same name, no scope
n8n-nodes-typesafe-ai
- Version
- 0.1.1, published (0.1.0 on 17 Sep)
- npm maintainer
dommonte(an address on montedev.com.au)- Repository field
DomMonte/n8n-nodes-typesafe-ai- SLSA provenance
- Yes, but to DomMonte's own repository (tags 0.1.0 and 0.1.1)
- n8n's community-node listing
- Not listed
- On n8n Cloud
- No: unverified, needs self-hosted n8n
"Third party" means only that TypeSafe does not publish it. Nothing found suggests the community nodes are malicious. Before installing any n8n node, check the npm maintainer and the provenance as above.
Why the names collide: the third party's package was on npm first
- Unscoped
n8n-nodes-typesafe-ai0.1.0 published (dommonte) - Unscoped 0.1.1, the latest version
- TypeSafe creates the GitHub repository
typesafe-ai/n8n-nodes-typesafe-ai - Scoped
@typesafe-ai/n8n-nodes-typesafe-ai0.9.0 published from tag 0.9.0 - n8n lists the scoped package as an official node
typesafe-ai organisation; all other dates from npm and n8n records read 3 Oct 2026. DocumentedCorrection to earlier pool pages
Earlier pool notes compared the GitHub tag 0.9.0 with the npm package n8n-nodes-typesafe-ai 0.1.1 as if they were one package, and the official vs reseller page said only that the npm publisher had not been checked. They are two packages from two publishers. The official one is the scoped @typesafe-ai/ package.
Can you use it on n8n Cloud?
n8n's documentation says: "Unverified community nodes aren't available on n8n cloud and require self-hosting n8n." n8n's public community-node listing had 1,765 entries when read on . The only Jev or TypeSafe entry was @typesafe-ai/n8n-nodes-typesafe-ai 0.9.0, marked as an official node and listed on 2 Oct 2026, 11:44 UTC. None of the four community nodes read for this page is listed, so on n8n Cloud only TypeSafe's node is available of these five. Documented
"n8n declined verification": one maintainer's claim
The maintainer of n8n-nodes-jev-classification (khmuhtadin, not one of the five read) wrote on the n8n forum on 26 Sep 2026: "n8n declined verification in September 2026 because of overlap with the built-in classification node that is in progress." n8n has not confirmed this. It does not show that n8n rejected any other node. Reported
What happens to your workflow when the Jev call fails
In all five nodes, n8n's "Continue On Fail" setting decides whether a Jev error stops the workflow or is passed on as an item. Choose a setting to see what the five nodes do with it; the matching column in the table below is outlined. Documented source at pinned commits, read 3 Oct 2026, 05:20–05:23 UTC; the official node's routing re-checked by the runner at 05:27 UTC
Off: 5 of 5 nodes stop the workflow
- 1. An item reaches the Jev nodeThe node sends the item's text (or the fields you chose) to Jev.
- 2. The Jev call failsFor example the official node throws
NodeApiErroron any HTTP status of 300 or more. - 5The workflow stopsOfficial, DomMonte, n8n-nodes-jev, taifoon and zampierid4p all throw. No item is sent down a decision branch.
This is the behaviour the key finding calls "by default": no item is routed. If Jev returns 429, the official node does not retry by itself; its README tells you to turn on n8n's "Retry On Fail".
On: where the failed item goes
- 1. An item reaches the Jev nodeContinue On Fail is on.
- 2. The Jev call failsThe node turns the error into an item instead of stopping.
-
3A real decision branch, unless a fallback output is setOfficial: Fallback or Uncertain output if configured, else the first route, the lowest Score level or Noul "False". n8n-nodes-jev: Low Confidence output if enabled, else the first route. zampierid4p: question 1's branch.1A Review outputtaifoon: the error item, with the key redacted and the input fields dropped1An error object onlyDomMonte: one output with
{error, description}; the input fields are dropped and nothing is routed
So with Continue On Fail on and no fallback output configured, the failed item arrives on a branch that real answers also use, such as Noul "False" or your first route. The official node and n8n-nodes-jev add an error field to that item; zampierid4p drops the input fields.
The official node in detail: where an error item goes with Continue On Fail on
| Route mode and setting | The error item (input fields plus error) goes to |
|---|---|
| Choice, with the low-confidence Fallback output | Fallback |
| Choice, without Fallback | The first route (output 0) |
| Noul, with the Uncertain output | Uncertain (the last output) |
| Noul, without Uncertain | "False" (the last output) |
| Score | The lowest Score level (output 0) |
nodes/TypeSafeAi/TypeSafeAi.node.ts L316–353 at c12537b, checked by the runner on 3 Oct 2026, 05:27 UTC. The code comment reads: "A failure is not a routing decision, so it goes to Fallback or Uncertain where one exists." Documented
Five nodes compared
Every cell comes from source at the commit shown or from npm metadata. Documented checked 3 Oct 2026. Licences: all five MIT. "COF" is Continue On Fail.
| Node (commit) | Publisher (provenance) | On n8n Cloud | Jev error, COF off | Jev error, COF on | Malformed answer | Timeout; retries | Data sent |
|---|---|---|---|---|---|---|---|
@typesafe-ai/n8n-nodes-typesafe-ai 0.9.0 (c12537b)Official. Evaluate; Route (Choice, Noul, Score) with optional Fallback and Uncertain outputs; usable as an AI tool. Tests: failure routing in test/execute.test.ts | TypeSafeGitHub typesafe-ai; npm alliesafe, diogo149 (typesafe.ai addresses); provenance to typesafe-ai tag 0.9.0 | YesVerified, official | fail-closed: stops the workflowapi.ts L109–115; TypeSafeAi.node.ts L331–333 | fallback-first route: real branch unless Fallback or Uncertain is setElse the first route, the lowest Score level or Noul "False" (L316–353) | fail-closed: throwsA Choice outside the routes or a missing Noul or Score answer (L106–110, L124–145). Evaluate passes answers through unvalidated (L276–281) | 5,000 msDefault, minimum 1,000. No retries in code; the README says to turn on "Retry On Fail" | State, model, questionsState is text by default; "Input Item" sends the whole item.json |
n8n-nodes-typesafe-ai 0.1.1 (DomMonte ff2afca)askNoul, askChoice, askScore, evaluate, list models. Base URL hard-coded. Tests: test/errors.test.ts | Third partyDomMonte; npm dommonte; provenance to DomMonte's repository | NoUnverified | fail-closed: stops the workflowL120 | no-decision: error object onlyOne output with {error, description}; input fields dropped (L109–117) | fail-closed: throwsOn a missing answer; evaluate unvalidated | Not setNo retries | State, model, questions |
n8n-nodes-jev 0.2.3 (vibe-with-me-tools ddbfe85)ask, route (choice, noul, score) with low-confidence options; editable base URL. Tests: yes, including COF | Third partyvibe-with-me-tools; npm brainsofbots; provenance yes | NoUnverified | fail-closed: stops the workflowJev.node.ts L181–182 | fallback-first route: real branch unless Low Confidence is onElse the first route (L168–179) | fail-closed: throwsUnknown or missing route (shared/route.ts L62–70) | 60,000 ms429 and 529: up to 3 retries, Retry-After or backoff up to 30 s | Text, JSON or the whole input item |
@taifoon/n8n-nodes-typesafe 2.0.5 (taifoon-io cdcc0f3)Ask, Translate; outputs pass, fail and review. Tests: template simulation and self-tests; no COF test found | Third partytaifoon-io (organisation); npm taifoon; provenance yes | NoUnverified | fail-closed: stops the workflowL75, L312–317 | fallback-review outputError item with the key redacted and the input dropped (L311) | fail-closed: throws by default"Fail Closed" is on by default; when off, the item "flows on as a null" (L159–160, L272–273). With no routing configured everything goes to pass (L305) | 60,000 msHard-coded. 429 and 529: 3 attempts | The whole item by defaultJSON.stringify($json) (L129); model jev-1.13.0 |
n8n-nodes-typesafe 0.3.3 (zampierid4p 549a545)ask, per question or as a single output. Tests: test/node.test.js (retries); COF only mocked as false | Third partyzampierid4p; npm zampierid4p; provenance yes | NoUnverified | fail-closed: stops the workflowL941, L956, L1065 | fallback-question 1's branchError item (input dropped) on output 0 in per-question mode (L1057–1063) | fail-closed: throws, or an empty branchA type mismatch throws; a missing answer leaves that branch empty (L990–1026) | Not set3 retries on 429, 529 and transport errors, up to 15 s each, 30 s budget | State, model, questions |
- fail-closed or held (a person or the host's own prompt decides)
- fallback-<what> (named in the cell)
- no-decision: nothing returned; the caller must handle it
Colours follow the shared legend on when Jev fails (changed ; this page used its own colours before). With Continue On Fail (COF) on, a blue fallback route can still be a real branch (3 of 5 nodes). Publisher, n8n Cloud, timeout and data-sent cells are facts, not verdicts, so they are uncoloured, here and in the count lines below.
Line numbers refer to each node's main file unless another file is named: nodes/TypeSafeAi/TypeSafeAi.node.ts (official and DomMonte), nodes/Jev/Jev.node.ts, nodes/TaifoonTypeSafe/TaifoonTypeSafe.node.ts, nodes/TypeSafe/TypeSafe.node.ts. Each repository path matches the package's npm repository field (re-read 3 Oct 2026, 05:28 UTC). Credentials: the official node stores the key in an n8n credential (password field), sends it as a Bearer token, hides the base URL (default https://api.typesafe.ai) and does not send the key on a redirect to another host (credentials/TypeSafeAiApi.credentials.ts L24–48; api.ts L105).
What the five rows add up to
Five n8n nodes read in source, one chip each
- Published by TypeSafe1 of 5
- TypeSafeofficial
- Third partyDomMonte
- Third partyn8n-nodes-jev
- Third partytaifoon
- Third partyzampierid4p
- Usable on n8n Cloud1 of 5
- Verifiedofficial
- Self-hosted onlyDomMonte
- Self-hosted onlyn8n-nodes-jev
- Self-hosted onlytaifoon
- Self-hosted onlyzampierid4p
- Jev error, COF off5 of 5 stop
- fail-closed: stopsofficial
- fail-closed: stopsDomMonte
- fail-closed: stopsn8n-nodes-jev
- fail-closed: stopstaifoon
- fail-closed: stopszampierid4p
- Jev error, COF on3 of 5 can reach a real branch
- fallback-first route (a real branch) unless fallback setofficial
- fallback-first route (a real branch) unless fallback setn8n-nodes-jev
- fallback-question 1's branchzampierid4p
- fallback-review outputtaifoon
- no-decision: error object onlyDomMonte
- Whole item sent1 of 5 by default; 2 more if chosen
- By defaulttaifoon
- If chosenofficial ("Input Item")
- If chosenn8n-nodes-jev
- State onlyDomMonte
- State onlyzampierid4p
How long each node waits for Jev before failing
Four rules for using a Jev node in n8n
- Install the scopedofficial: scoped, provenanceDomMonte: same name, no scope
@typesafe-ai/n8n-nodes-typesafe-aiif you want TypeSafe's node.Not the unscoped
n8n-nodes-typesafe-ai. Before installing any node, check its npm maintainer and provenance. More on telling official surfaces apart: is this Jev site official? - Leave Continue On Fail off, or turn on a fallback output with it.official, n8n-nodes-jev, zampierid4p: real branch possibletaifoon: Review output
If you turn it on, also enable the Fallback (Choice) or Uncertain (Noul) output, or route errors to n8n's error output. Otherwise a failed Jev call can land on your first route or on "False". How n8n's error output handles this is known only from the official node's code comment.
- Set the timeout on purpose.5 s or 60 s2 nodes: not set
The official default is 5 s. If you use the official node, add n8n's "Retry On Fail" for 429s; the node does not retry. Rate limits and retry advice: errors and rate limits.
- Send only the fields Jev needs.taifoon: whole item by defaultofficial, n8n-nodes-jev: if chosen
Avoid "Input Item" and whole-item modes for personal data. What leaves your system on each route: data handling by route.
The rules are a design reading of the source above, not a tested result. None of the five nodes documents pinned test data; for testing failure paths without a key, see testing without a key.
How the five were chosen
15 Jev and TypeSafe n8n packages found on npm on 3 Oct 2026: 5 read, 10 not read
- 1 official, read
- 4 community, read
- 10 community, found but not read
The official node, typesafe-ai/n8n-nodes-typesafe-ai, was read at tag 0.9.0 (commit c12537b, the repository's only tag; last push 29 Sep 2026, 21:11 UTC). The four community nodes were picked from npm registry searches for "n8n-nodes jev", "n8n typesafe" and n8n community-node packages with the keyword "jev" (3 Oct 2026, 05:20–05:22 UTC), preferring packages with a public repository. That is a reading order, not a sample, and the 15 found is not a survey of all Jev n8n nodes. Each node was read from raw files at one pinned commit by a helper agent briefed with the table's columns; the runner spot-checked the official node's error routing, both npm maintainer records and the n8n listing against the same sources. No node was installed, no package was unpacked, no workflow was run and no Jev call was made. Repository stars were not fetched.
The query phrase comes from Google suggest ("jev n8n", "jev n8n github") and YouTube suggest ("jev n8n"), both at 05:24:12 UTC; Google also offered "typesafe n8n github" and "typesafe n8n example" for "typesafe n8n". Bing and DuckDuckGo gave no Jev n8n suggestion. A video tutorial, "How To Setup JEV With n8n", is in the n8n videos group.
Other no-code tools: Zapier
Zapier lists a "TypeSafe Jev" app with one action, "Ask Questions" (checked 5 Oct 2026, 05:21 UTC). Documented The page does not say who built it and shows no date. Failure behaviour is not readable in source (Zapier is a closed platform): not recorded. It is not counted here or on when Jev fails.
What was not verified
- How n8n itself handles a node's "error output" setting: this page knows it only from a code comment in the official node.
- The 10 Jev and TypeSafe n8n packages found on npm but not read.
- Whether n8n declined verification for any node: one maintainer's claim only (Reported).
- How any node behaves live: nothing was installed and no workflow was run. Every cell is a reading of source code or registry metadata.
- The community repositories' GitHub stars, and how many people use any of these nodes.
- Who built the Zapier "TypeSafe Jev" app, and what a Zap does when the Jev call fails.
Sources and check times (3 Oct 2026, UTC)
- npm, official package (05:20:53; attestations 05:21:32; maintainers re-read 05:27): registry record and attestations for 0.9.0 (provenance commit
c12537bbd9ed7159b7bbe23678ca128c7b2fb52b). - npm, unscoped package (05:20:25; attestations 05:20:33): registry record and attestations for 0.1.1 (gitHead
ff2afca). - n8n docs (05:23:10): community nodes installation.
- n8n community-node listing (05:27:14): api.n8n.io community nodes, 1,765 entries.
- n8n forum (05:23:35): thread 316451, post of 26 Sep 2026 (Reported). Forum search for "jev" returned HTTP 429.
- Official node at c12537b (05:20:40; L316–353 re-checked 05:27):
TypeSafeAi.node.tsL37–38, L106–145, L267–281, L316–353;api.tsL105–128;descriptions.tsL30–32, L182–197, L486–489;credentials/TypeSafeAiApi.credentials.tsL24–48. Tags and organisation: GitHub tags API (05:15:30). - DomMonte/n8n-nodes-typesafe-ai at ff2afca:
TypeSafeAi.node.tsL77–178 (05:22:00). - vibe-with-me-tools/n8n-nodes-jev at ddbfe85:
Jev.node.tsL135–219;shared/transport.ts;shared/route.tsL62–70 (05:22:30). - taifoon-io/n8n-nodes-typesafe at cdcc0f3:
TaifoonTypeSafe.node.tsL41–75, L118–160, L250–320 (05:23:00). - zampierid4p/n8n-nodes-typesafe at 549a545:
TypeSafe.node.tsL17–63, L371–392, L919–1065 (05:23:30). - 5 Oct 2026: Zapier "TypeSafe Jev" app page (05:21:14 UTC, R8-S120).
- Selection: npm registry searches (05:20–05:22). Query wording: Google and YouTube suggest (05:24:12), Bing and DuckDuckGo autocomplete.