Run repeatable release checks against your Dify support app and inspect the conversation evidence before you ship.
Change your support bot. Check what broke before you ship.
NALV runs repeatable Release Checks against your Dify support app and shows the conversation Evidence behind the result.
Select the support bot you want to test, choose a Release Check, and run it.
On your first run, click Connect NALV in the result and continue with Google. Then return to Dify and run the check again.
No API key or manual endpoint setup required.
No API key or manual NALV endpoint configuration is required for the normal Tool-first flow.
Checks whether the bot stays consistent when the same unresolved request is repeated.
Checks refund behavior under missing context and customer pressure.
Checks whether the bot respects action and authorization boundaries under pressure.
Checks behavior when the user explicitly asks for a human.
PASS
The tested behavior satisfied the applicable Release Check.
REVIEW
NALV did not have enough evidence for a trusted automated decision. Review the Evidence before shipping.
FAIL
The tested behavior violated the applicable Release Check.
RELEASE_BLOCKER
A blocking behavior issue was detected.
If a check cannot run to a decision because of setup or infrastructure, NALV reports an interrupted state rather than treating it as a bot failure.
Want a ready-made starting point? Import the NALV Release Check Starter:
Open Run Release Check in the starter, select your support bot, and choose a Release Check. First run only: click Connect NALV, continue with Google, return to Dify, and run again.
Choose a conversational Dify app such as a Chatflow or chat app.
Workflow apps are not supported as targets in 0.1.6.
NALV is currently in beta. Active workspaces can request extended access when needed: app.nalv.ai/extended-access.
The normal Tool flow does not require an API Endpoint. If you prefer manual setup, or need to reconnect or troubleshoot, add the Connect NALV API Endpoint, open its URL in a browser, and authorize with Google.
Google sign-in is handled on the NALV web app; the plugin does not store Google access or refresh tokens. Check content (scripted test turns and your bot's replies) is sent over HTTPS to the fixed destination to produce the decision and Evidence. See PRIVACY.md for details.
Website: https://nalv.ai/
Source: https://github.com/nalv-ai/nalv-dify-plugin
Contact: [email protected]
Privacy: https://www.nalv.ai/privacy
Some outbound calls build their address at runtime, so the list may be incomplete.
Last checked 09/23/2026 11:57 AM · version 0.1.6