Choosing a Workflow Stage
Formie's six stages have fixed responsibilities and order. Extend the appropriate stage with a task when your project needs an additional check or action.
Suppose an order needs a project-specific reference check after ordinary field validation. Register a Submit task after validate.submission. Invalid input then stops before spam checks, CAPTCHA or saving the submission. The custom task walkthrough builds and tests that example in a Craft module.
Choose When the Task Runs
| Work | When to Run |
|---|---|
| Validate accepted field values before screening | After validate.submission |
| Evaluate a content policy before CAPTCHA | Before screen.verifyCaptcha |
| Read the saved submission before payment processing | After persist.submission |
| Enqueue work before integrations | Before dispatch.triggerIntegrations |
| Read the final submission result | After the Finalize stage |
Formie registers task IDs, handlers and applicable operations together. Choose Submit, SaveDraft, Revise or PaymentReplay explicitly. A task can use TaskResult::continue() or stop with a typed outcome; stage/task observation events cannot cancel execution.
Use prepend() or append() when a stage boundary is sufficient. Use a supported task ID when another task must run immediately before or after yours. Internal steps such as checking page navigation and preparing a save cannot be used as task IDs. Extensions cannot replace or reorder stages.
After adding the task, test the intended operation and an operation that should skip it. For example, a Submit validation rule should reject the relevant input on submission while allowing a draft to save. The workflow reference lists the supported task IDs and explains version conflicts and retries.