Build workflows
Last updated August 28, 2026
Define what happens after someone submits, including reviews, appointments, assessments, approvals, payments, and handoffs.
This is probably the most important future capability because it turns Intake from forms into a process engine.
Status: Planned
Define the stages
Example school enrollment:
Application → Review → Assessment → Decision → Registration payment → Enrollment
Example massage:
Booking → Deposit → Confirmed → Appointment → Completed
Example medical center:
Appointment request → Review → Confirmation → Visit → Follow-up
Decide what can happen at each stage
A workflow step might:
- collect more information
- require payment
- request documents
- send a message
- require staff review
- schedule an appointment
- approve or decline
- hand off to another system
Move submissions automatically
Eventually conditions could drive transitions:
- Payment received → move to Confirmed
- Application approved → request registration fee
- Required documents uploaded → move to Review
This is where the system starts becoming much more powerful than simply a form builder.
Use ready-made workflows
I would connect this back to templates.
A template can provide a default workflow:
- School enrollment template — Application → Review → Decision → Enrollment
- Service booking template — Request → Payment → Confirmation → Appointment
Then organizations can customize it later.