NALV
Verified by DifyBehavior verification for Dify Chatbot and Chatflow customer-support apps. Run a NALV check, inspect evidence, and retest after you fix behavior.
NALV for Dify
NALV verifies customer-support bot behavior.
The loop is:
Change something → Run a Check → inspect Evidence → fix behavior → Check again.
This plugin is not observability, chatbot scoring, a red-team toolkit, a Dify agent builder, or a generic LLM-as-judge product.
What this plugin does
The plugin connects a Dify Chatbot or Chatflow to a NALV workspace.
When you run a check, it:
- Asks NALV for the frozen customer turns for that check.
- Reverse-invokes the selected Chatbot or Chatflow with those turns.
- Submits the observed assistant replies to NALV.
- Returns NALV's evidence link and decision.
NALV owns planning, evaluation, and the stored run. The plugin does not score the bot itself.
Installation and setup
- Install NALV from the Dify Marketplace, or upload the from a NALV release.
- Add the NALV Endpoint.
- Select the Chatbot or Chatflow to verify. Agent, New Agent, and Workflow apps are rejected as an unsupported target. That is not a behavioral FAIL.
Connect with Google
- Open the Endpoint URL Dify shows (path ) and click Connect NALV.
- Continue with Google on NALV. A personal workspace is created automatically if you do not have one.
- Return to Dify. The Endpoint should show NALV connected.
You do not copy or paste a NALV connection key. Google credentials never enter this plugin.
How to run a behavior check
- Confirm NALV is connected and a Chatbot or Chatflow is selected.
- Submit the Endpoint form, or JSON such as .
- Open the returned Evidence URL in NALV. If you completed Connect in the same browser, Evidence opens without a second login.
The current hosted check uses a frozen three-turn customer script. NALV decides PASS / REVIEW / FAIL / RELEASE_BLOCKER from evidence. Infrastructure or evaluator failure stays REVIEW and is not treated as a behavioral FAIL.
Disconnect
Click Disconnect NALV on the Endpoint page. That removes the connected state in Dify and asks NALV to revoke the active plugin surface token. Existing check runs remain available in NALV. Reload the Endpoint to confirm it stays disconnected until you Connect again.
What data is sent to NALV
Connect sends a one-time connect session and, after Google sign-in, stores a scoped NALV surface token in Dify plugin session storage. Checks send the NALV-issued customer turns, observed assistant replies, conversation id, and Dify app id/mode to . The destination is fixed and not configurable.
The plugin does not send Dify workspace API keys. See PRIVACY.md.
Current capabilities and limits
Supported:
- Dify Chatbot () and Chatflow ( / )
- Connect NALV with Google identity
- Automatic personal workspace
- Blocking reverse invocation
- One conversation id reused across the frozen turns
- Evidence stored and evaluated by NALV
Not claimed and not included:
- Complete behavioral coverage
- Guaranteed correctness
- Production certifications
- Agent / Workflow targets
Manual / advanced setup
A NALV connection key setting remains as an optional fallback for local development and troubleshooting. Prefer Connect NALV. Do not use a Dify Remote Debug key, Dify app API key, or invite token as that setting.
Support
- Support: [email protected]
- Privacy: [email protected]
- Privacy policy: PRIVACY.md
- Source: https://github.com/nalv-ai/nalv-dify-plugin
Some outbound calls build their address at runtime, so the list may be incomplete.
Last checked 09/02/2026 12:50 PM · version 0.1.4