WP Suite Flow – WordPress Forms, Discussions, Ratings & Workflows

A form submission rarely finishes the job. Applications need saved progress, reviews move into email, and comments or scores become disconnected from the underlying record. Static publishing adds another obstacle: forms, discussions and ratings still need somewhere to store and update their state.

Flow brings these interactions together in WordPress. Build the experience in Gutenberg and connect persistent submissions, discussions, ratings and workflow actions to an optional backend in your own AWS account. The public page can remain static while the interactions stay live.

• Build multi-step applications, onboarding and intake forms with conditional paths, validation and uploads.
• Let users save and resume long forms through a compatible backend, rather than starting again.
• Submit from the browser to a configured endpoint; simple forms do not require deployment of the Flow AWS backend.
• Use dynamic field sources and optional API-backed, AI-assisted guidance before submission. Users remain responsible for confirming their input.

• Attach content-bound discussions and nested replies to the relevant WordPress page or record.
• Configure moderation, participation rules and supported owner actions.
• Collect ratings through Flow forms and display backend-calculated totals and distributions using the Rating Summary block.
• Keep discussion and rating state in a separate backend, including when the page is published statically.
• Add Gatey/Amazon Cognito identity where authenticated participation or group-based access is required.

A submission may begin a review, approval or follow-up process rather than end at data collection. Configure a customer-owned Flow backend for durable drafts and submissions, workflow state, notifications, webhooks, AWS EventBridge routing and downstream automation. Connect review discussions and scoring to the same content context when the process calls for them.

Moving WordPress to static delivery should not mean losing every interactive feature. Flow components can run in the visitor's browser and communicate with configured services for forms, saved state, discussions, replies, ratings and workflow actions—without relying on public WordPress/PHP requests for these interactions.

Use Flow alongside WP Suite Static Publisher for static page delivery, Gatey for optional Cognito identity and AI-Kit where AI or knowledge search is needed. Each component is optional and has a distinct responsibility.

Flow works as a Gutenberg form builder without a mandatory AWS backend. Choose an external submission endpoint for simpler use cases. Where persistent state or richer workflows are needed, deploy the supported Flow backend in your own AWS account.

A configured deployment can use API Gateway, Lambda, storage, EventBridge, webhooks and optional authorization through Cognito/JWT or IAM. Availability of individual features depends on the connected backend and configuration.

• Long applications and client onboarding requiring save and resume.
• Replacing email and spreadsheet-based review handoffs.
• Content-bound discussions, feedback and ratings.
• Approval or scoring workflows with notifications and downstream actions.
• Interactive forms and comments on static/headless WordPress sites.
• API-integrated forms with dynamic choices and optional pre-submit guidance.

Smart Cloud Solutions provides remote implementation and integration services:

• Form & interaction architecture: Gutenberg forms, branching, save/resume, discussion, moderation and ratings.
• Workflow design: Review and approval states, routing, webhooks, EventBridge, email and automation.
• AWS backend deployment: Configure the supported Flow backend in your account, including security, monitoring and integration endpoints.
• Static-site enablement: Keep browser-side interactions working after WordPress is published statically.
• Migration & rollout: Replace fragmented forms and manual processes, test permissions and data flows, and prepare production deployment.

AWS infrastructure and usage charges, where applicable, remain in the customer's AWS account. Backend-connected capabilities require a compatible, properly configured backend.