JevMade field notes / Technical guide

Add Jev questions to a Node-RED automation

Node-RED builds automations by connecting message-processing steps. This add-on asks Jev questions about a message and makes both answers and failures available to later steps.

Original by ayaliIntegrations

Bookmark Keep this in your collection.

Leave a noteWhat would you try with this?

Only you can see your notes.

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Independent ElevenLabs affiliate. JevMade may earn a commission.

Credits and license

“@ayali/node-red-contrib-jev” by ayali. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 Ayal Itzkovitz

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

Node-RED builds automations by joining steps that pass messages between them. This add-on supplies a secure place for service credentials and a Jev question step. That step can ask several questions about one message and return named answers for later steps to use.

The guide shows a first connected workflow and explains how questions can be fixed or supplied by a message. Examples classify camera events and place a Jev check before a larger AI model, deciding whether more processing is needed.

Questions built from incoming messages can expose more information than intended. Limit what is sent, check how questions are formed, and connect the failure route as well as the success route. Decisions about cameras or safety need cautious rules rather than trust in one estimate.

Key takeaways

Keep the private key in the credentials step, not in messages.
Related questions can read the same message together.
Connect the failure output so an unavailable answer has a defined response.

More guides →See the experiments →