Make webhook form builder
Use FormNode as the workflow-ready form layer in front of Make scenarios when requests need dynamic fields, approvals, portal context, and structured webhook payloads.
A Make webhook form builder collects structured user input and sends it to a Make custom webhook. FormNode is the better fit when the form also needs live dropdowns, approvals, customer portal context, tenant mappings, and delivery visibility before Make runs the scenario.
Use FormNode when the form needs workflow context before the webhook fires.
- You already use Make scenarios for fulfillment but need a stronger customer-facing form layer.
- The form needs live options from an API, PSA, RMM, Microsoft 365, or another source system.
- Approvals should happen before the Make scenario mutates systems.
- The same form should carry customer or organization context across many clients.
Make the form contract explicit before fulfillment.
Create the FormNode form
Build stable field keys for the request Make will receive.
Add dynamic fields where needed
Point dropdowns at read-only Make webhooks, n8n webhooks, or source-system APIs.
Configure the Make webhook
Use a separate Make custom webhook for final submission fulfillment.
Test the payload
Submit the real form and confirm Make receives IDs, labels, organization context, and approval state.
Frequently asked questions
Can FormNode send submissions to Make?
Yes. FormNode can send structured submissions to a Make custom webhook, including selected field values, labels, organization context, approval state, and metadata.
Should Make handle dynamic dropdown options?
It can. Keep those webhooks read-only and separate from the final submission scenario that changes systems.