Submissions & Workflows
Submission lifecycle, statuses, screening, reports, and rendering stored content.
Editing submissions on the front end
Formie can render a saved submission back into the form so someone can update it from the front end — account areas, application review flows, or any case where data may change after first submit.
Relations between submissions and entries
Submissions can be related to Craft elements — entries, categories, products, users — so form data stays connected to the content it belongs to. Relations are set in Twig before render, not chosen manually by editors in the form builder.
Saved reports and scheduled delivery
Getting-started walkthrough for saved reports and scheduled email delivery — links to the reports reference for formats, permissions, cron, and troubleshooting.
Submission screening rules in practice
Submission screening is Formie's unified layer for deciding whether a submission is legitimate before it is saved and dispatched. This guide shows how guards, captchas, and content rules work together in practice — and how to tune them without blocking real users.
Submission statuses and conditional workflows
Submission statuses are team workflow labels on saved submissions. Conditions change what the form shows and which notifications send based on answers. Together they let you route work after submit and tailor the form experience before submit.
Submission workflow and stages explained
Formie runs every submission through a staged pipeline. This guide explains what each stage does, which requests run the full flow, and how to think about hooks before you write PHP.
Using submission workflow events
Most extensions only need workflow event listeners — validation tweaks, post-save sync, blocking dispatch on test forms — without custom task or stage classes. This walkthrough wires the common patterns from a Craft module.
Adding a custom workflow task from scratch
When one ordered step inside an existing stage is what you need — before integrations, after spam checks, and so on — register a custom task and insert it relative to a built-in anchor. This walkthrough queues an internal review job before CRM dispatch.
Adding a custom workflow stage from scratch
When you need a new phase in the pipeline — not just another task inside screen or dispatch — register a custom stage. This walkthrough adds a fraud score check after spam screening and before authorization.
Save and continue later
Long and multi-page forms lose completions when visitors get interrupted. Formie stores incomplete submissions in the database, optionally exposes a save button with resume links, and can restore in-progress state automatically when someone returns. This walkthrough configures the feature end-to-end for a job application or registration form.