Rewst form migration template for n8n
A practical form-migration outline for MSPs rebuilding Rewst forms in FormNode while moving workflow execution into n8n.
A Rewst form migration template should inventory the original form fields, dynamic option sources, organization variables, conditional behavior, approval points, and workflow trigger payload before rebuilding the form in FormNode and wiring n8n webhooks.
Use this template when the form is part of an operational workflow.
- MSPs moving Rewst-style forms to FormNode plus n8n.
- Teams that want to migrate one high-value workflow at a time.
- Operators who need a replacement plan without publishing their workflow exports.
Typical systems this template may need to read before n8n fulfills the request:
Fields this form should include
Treat Rewst approval-like behavior as an explicit migration item. Rebuild it as FormNode approvals when a human decision must pause n8n.
Do not reuse mutation workflows as dropdown endpoints. Build read-only n8n endpoints for dynamic options and a separate final submission webhook.
Build the form first, then wire the workflow.
Export or document the source form
Capture fields, labels, dynamic behavior, conditions, and workflow trigger expectations.
Rebuild the form fields
Create stable FormNode fields and preserve the payload names n8n will need.
Map dynamic options
Replace Rewst dynamic options with read-only n8n webhook dropdowns.
Test side by side
Submit a test response and compare the new n8n payload against the old workflow requirements.