ValGuard.ai logoValGuard.ai

Migrate Flowise chatflows to ValGuard playbooks

What the ValGuard importer maps from Flowise exports, what it skips, and the post-import checklist before enforce.

ValGuard can import Flowise chatflow exports into a playbook draft via the dashboard migration wizard. This page states what maps, what does not, and the checklist before you enforce rules on production traffic.

What imports

Flowise conceptValGuard mapping
Chatflow / graph export (flowise/chatflow/1.x)Playbook draft with steps
LLM / chat nodes (OpenAI-compatible style)Agent-backed steps
Linear and branching structure (supported subset)Routes in the playbook graph

Converter id: flowise/2026-08-v1. Detection looks for Flowise node graphs in the export JSON.

What does not import (or needs rework)

  • Custom Function / Tool nodes that call arbitrary code without an OpenAI-compatible hop
  • Flowise-specific memory and UI widgets with no ValGuard equivalent
  • Credentials and API keys (re-enter in Provider Vault / BYOK)
  • Canvas-only triggers (webhooks, schedules) as n8n-style connectors

Keep Flowise or n8n for connectors if you still need them. Point LLM hops at ValGuard. stack map.

Mapping table (mental model)

flowchart LR
  F[Flowise export JSON] --> W[Migration wizard]
  W --> D[Playbook draft]
  D --> V[Attach validators]
  V --> S[Shadow]
  S --> E[Enforce]

Run the importer

  1. In the dashboard, open the migration / import wizard and choose Flowise.
  2. Upload the chatflow export JSON.
  3. Review detected nodes and the draft graph.
  4. Create or bind agents; attach packs.
  5. Save as draft; do not enforce yet.

Post-import checklist

  • Every LLM step has an agent slug and packs.
  • Shadow mode on for a week of synthetic or sanitized traffic. Shadow mode.
  • Fail-closed path defined for blocks. Fail-closed.
  • Provider keys in vault; no secrets left in the Flowise file.
  • Playbook export JSON backed up (valguard-playbook-template/1).
  • Human escalation edges where high-risk actions need approval.

Honest limits

  • Import is best-effort graph translation, not a 1:1 runtime of Flowise.
  • You still need ValGuard agents and validators; Flowise nodes are not policy.
  • Org-wide policy file export is not available yet; portability is per playbook / per agent. Trust.

Related

Next step

Export a non-production Flowise chatflow and run the wizard. Attach one schema pack in shadow before enforce.