Automation engine

Make forms for webhook-driven workflow intake

Use FormNode as the customer-facing form, portal, and approval layer before sending structured requests into Make scenarios.

Build this workflowSee related setup
Direct answer

FormNode gives Make a stronger form layer: Make runs the scenario, while FormNode handles dynamic dropdowns, approvals, customer portal access, tenant context, and predictable webhook payloads.

Webhook-native submission deliveryMake workflows stay structured, tenant-aware, and automation-ready.
Dynamic fields before scenario executionMake workflows stay structured, tenant-aware, and automation-ready.
Approval state in the payloadMake workflows stay structured, tenant-aware, and automation-ready.
Workflow fit

Use FormNode when the request needs more than a static form.

  • Make custom webhook forms
  • Approval-before-scenario workflows
  • Customer portal request forms
  • Dynamic dropdowns backed by Make or source-system APIs
Example workflow

A FormNode customer portal form collects a service request, captures approval, and sends a structured payload to a Make custom webhook that updates the CRM, posts a notification, and creates the work item.

Useful fieldsCustomer, Requester, Approval, Request type, Source-system ID, Priority
Why FormNode fitsWebhook-native submission delivery, Dynamic fields before scenario execution, Approval state in the payload, Portal context outside Make
Common questions

Can FormNode send forms to Make?

Yes. FormNode can send final submissions to a Make custom webhook with field values, labels, approval state, organization context, and metadata.

Does FormNode replace Make?

No. FormNode handles the form, approval, portal, and webhook delivery layer. Make remains the scenario and fulfillment engine.

Related FormNode pages