Configure Smart Flow Steps
Choose the right step and connect the record that completes it.
Each Smart Flow step has content and completion settings. Some finish when the recipient continues; others wait for a linked form, booking, document, payment, or upload.
Available steps
| Step | What to configure | What completes it |
|---|---|---|
| Info / video | Instructions, context, or video | Recipient acknowledgement |
| Page | Content blocks, text, images, video, and layout | Recipient acknowledgement |
| Questionnaire | A form or intake questionnaire | Form submission |
| Scheduler | A booking page | A booking |
| File upload | Requested files, limits, and destination folder | Required upload evidence |
| Proposal | A proposal document template | Acceptance of the generated proposal |
| Contract | A contract document template and signer settings | Required signing event |
| Payment | The invoice to collect | The linked payment event |
Linked records must belong to the workspace and be available for the selected step. A proposal needs a proposal template; a contract needs a contract template. Resolve missing, deleted, or incompatible records before publishing.
File requests
Describe what the recipient should provide. Add requested files and mark required items, then set allowed file types, size limits, maximum file count, and the destination folder.
Keep the maximum file count large enough for all required requests. Upload completion depends on the requested evidence, not merely opening the page.
Content and progression
Set Own focused page when a step should have its own full-screen page. Review Required to continue and the button label so the recipient knows what to do next.
After the first step, choose Continuous delivery to open the step after the previous one, or Hold until released by workflow when an automation must release it. A held step needs a published Workflow using Make next Flow step available. Without that release, the client will keep waiting.
See Connect Workflows and client flows for the release action and related waits.
Review the complete journey
Preview content before delivery. For a real run, review the resulting form submission, booking, document, upload, or invoice as well as flow progress. A successful page preview does not establish that a client signed or paid.