Skip to main content

Flow Overview​

Flow is a block-based forms and workflow plugin for WordPress.

It combines a Gutenberg-based form builder with a React/Mantine runtime and an optional AWS backend. In its simplest setup, each form submits directly from the browser to the endpoint URL configured for that form. That endpoint can be your own custom service, a WordPress-side endpoint you implement yourself, or the Flow backend submission endpoint.

Recent Flow builds cover more than plain single-screen forms. The current editor and runtime support:

  • wizard-style multi-step forms,
  • standalone success states,
  • draft save/load flows,
  • AI suggestion blocks with accept/reject/continue behavior,
  • client-side runtime events for submissions, drafts, wizard navigation and AI actions,
  • backend sync into a canonical backend form definition,
  • event-driven workflows, templates and manual actions in Pro mode.

Free vs Pro​

Free​

Free mode does not require a hosted SaaS backend or a WPSuite connection.

With Free mode you can:

  • build forms in Gutenberg,
  • use wizard and success-state layouts,
  • use layout and field blocks,
  • apply conditional logic,
  • run AI suggestions inside the frontend runtime when your site ships the required AI backend wiring,
  • reuse forms via shortcode or Elementor,
  • submit directly from the browser to the endpoint URL configured on the form.

Flow does not inherently store submissions in WordPress. If you want submissions handled inside WordPress, you need to implement your own receiving endpoint.

Pro​

Pro becomes available after connecting your WordPress site to a WPSuite.io workspace. It is designed to work especially well with the separately deployed WP Suite Flow Backend in your own AWS account.

A typical Pro setup is:

  1. deploy the Flow backend to AWS,
  2. add its published API base URL to Gatey as a separate API,
  3. choose the matching protection mode (IAM or COGNITO),
  4. select that API in SmartCloud → Flow Settings → API Settings.

This gives you a simpler secure setup for backend-aware submissions, admin tooling, templates, workflows, and related automations.

In practice, Pro is where Flow becomes a submission and automation platform instead of only a frontend form renderer. Typical Pro-only patterns include:

  • durable submission storage and searchable submission history,
  • draft persistence and resume,
  • backend form sync and schema tracking,
  • email templates and templated replies,
  • event-driven workflows and manual actions,
  • AI-agent workflow steps and downstream routing,
  • EventBridge/webhook handoff to other systems.

AI and workflow patterns​

Flow's runtime can collect AI suggestions in the browser, and the backend workflow layer can also orchestrate AI agent steps after a submission has been accepted.

That split is intentional:

  • AI Suggestions block: helps the end user before final submission by proposing answers, next-best actions and related documentation.
  • AI Agent workflow step: runs after an event enters the backend workflow system and can classify, route or enrich a submission.

The backend AI step now has its own configuration surface for routing presets, schema constraints, and downstream process-map branching. If you are configuring it for the first time, read AI Agent Workflow Step before designing route keys or response schemas.

Those backend workflows are not limited to browser-originated forms. The same Flow workflow engine can also consume normalized events coming from AI Kit Backend email-intake pipelines, so the same templates, routing rules and downstream steps can serve both web forms and inbound emails.

What this documentation covers​