## Flow Overview

Flow is a Gutenberg-native forms and workflow system for WordPress. It combines a block editor experience with a single React runtime and an optional backend that you deploy into your own AWS account.

In Free mode you can build forms, use wizard and success-state layouts, apply conditional logic, theme the runtime and submit directly from the browser to the endpoint URL defined on the form.

In Pro mode Flow can also:

- sync form definitions into the backend,
- store submissions durably,
- save and resume drafts,
- manage templates and submission history,
- run event-driven workflows,
- invoke AI agent workflow steps,
- fan out into webhook or EventBridge automations.

Flow's frontend runtime also now exposes lifecycle events for drafts, wizard step changes, AI suggestion decisions, successful submissions and success-state rendering. On the AI side there are two distinct layers: the frontend AI Suggestions block helps the user before submit, while backend `ai.agent` workflow steps classify or enrich accepted events after they enter the automation layer.

The backend AI step is not a decorative placeholder. The current admin UI really does support:

- task intent selection via `Mode`,
- optional Flow-owned routing presets,
- route, outcome, and signal key authoring,
- editable prompt and system-guidance fields,
- JSON-schema response constraints,
- downstream branching through `ai.agent.completed` / `ai.agent.failed` and process-map step-trigger projections.

Operationally, this only works end-to-end when Flow backend and AI Kit backend are both present. Flow backend emits the workflow-side `ai.agent.requested` event, while AI Kit backend contains the dispatcher that turns that request into `ai.agent.completed` or `ai.agent.failed`. If AI should use knowledge-base evidence, the AI Kit backend also needs a configured model and an available Knowledge Base with ingested documents.

Practical note:

- `No internal routing` removes the platform routing guardrail block, but it does not automatically clear any older custom response schema left in the editor.

That workflow layer can serve both browser submissions and normalized AI Kit Backend email-intake events, so Flow is increasingly the shared orchestration surface for form and email-driven intake flows.