Capture customer context and map it into the payload your automation expects.
Know what happened after someone submits the form.
FormNode keeps the form, customer context, approval state, and webhook delivery status connected, so your team can troubleshoot the workflow without digging through logs.
organizationId: org_contosoapproval.status: requireddelivery.status: pendingSee whether the webhook delivered, failed, or needs attention.
Use submission and delivery history to tighten the workflow over time.
Client-facing on the outside. Automation-native underneath.
A real Microsoft 365 user onboarding flow — branded form, customer context, live dropdowns, approvals, and webhook workflow — built with Claude over the FormNode MCP server. This example uses n8n, but the same pattern works with any platform that accepts webhooks.
Build our Microsoft user onboarding form and the webhook workflows behind every dynamic dropdown. Filter the org dropdown to active managed-services customers from ConnectWise. Pull licenses from CIPP with available counts. Wire the submit workflow to provision the user via CIPP, apply the Sherweb license, copy settings from the selected user, and open a ConnectWise ticket.
What the agent built
- Microsoft 365 user onboarding form with dynamic dropdowns wired to ConnectWise organizations, CIPP licenses, and the tenant
- Real-time username validation against the customer's tenant
- Office location dropdown that auto-fills the address fields from ConnectWise sites
- Provisioning workflow that runs through n8n in this example, applies the Sherweb license, copies settings, and opens a ConnectWise ticket
- Companion offboarding flow built next using the same pattern
Your old form builder was only half the job.
FormNode treats the customer-facing form, live data, approvals, portals, and webhook workflows as one connected system.
Your agent builds the client-facing form and the workflow
Connect Claude or Codex to FormNode's MCP server and your webhook platform. The agent creates the fields, wires dynamic dropdowns, and ships the backing workflow instead of handing you a polished form with no workflow depth.
Fields, pages, validation, required values, and customer context.
ConnectWise, CIPP, Hudu, NinjaOne, Graph, or any webhook-backed source.
Submission routing, approval callbacks, provisioning steps, and retry handling.
Live data at the field level
Dropdowns call your webhook, parse the response, and stay scoped to the selected customer, tenant, or ticket.
Approvals stay in motion
Decision tables and email approvals call back into the workflow without forcing every approver into a portal.
One customer portal per client
Each organization gets isolated forms, submissions, and portal context. Pro adds custom domains; Business adds full branding and white-label controls.
Native n8n support when you want it
Use the official n8n community node, or send submissions and dynamic-field calls to any webhook endpoint.
Failures are visible
Webhook delivery status, retries, payloads, and responses are tracked so workflow breakage is not silent.
Workspace isolation built in
RBAC, workspace scoping, rate limits, encrypted data, and HTTP-only sessions are part of the product contract.
Generic form builders collect answers. FormNode starts workflows.
If a form touches IT, it needs more than fields and a webhook URL. It needs live system data, tenant context, approval state, delivery visibility, and a payload your automation stack can trust.
Nice-looking form, thin handoff
- Looks fine on a web page but hands IT a flat payload
- Live customer data needs custom glue outside the form
- Approvals happen in a separate tool or a ticket comment
- Webhook failures disappear unless someone checks server logs
Workspace-aware workflow payload
Two paths to a working form.
Click the canvas yourself, or hand the keys to Claude. Either way, the result is presentable to customers and useful to IT.
Build it yourself
Drag fields onto the canvas. Point any dropdown at a webhook URL — your PSA, RMM, CIPP, Hudu, or anything else with an HTTP endpoint. Publish to your customer portal or a direct link.
Five minutes for a simple form. An hour for one with cascading dropdowns and approvals — including the webhook workflows behind them.
Have an agent build it
Connect Claude or Codex to FormNode's MCP server and your automation stack. Describe the form. The agent builds it, wires the dropdowns, and builds the webhook workflow that runs on submit.
Same form. Same five minutes. You just talked instead of clicked.
Frequently asked questions
What MSPs ask before they pick a form builder.
What is FormNode?
FormNode is a form platform for IT automation teams. It gives you client-ready forms and portals that can call your webhooks to populate dynamic dropdowns, route submissions through decision-table approvals, and preserve customer or tenant context. It is used primarily by MSPs and IT teams to run onboarding, ticket intake, and approval workflows against systems like ConnectWise, NinjaOne, CIPP, and Microsoft 365.
How is FormNode different from Jotform, Formstack, or Cognito Forms?
Generic form builders collect answers. FormNode starts workflows. It is built around three things those tools either bolt on or charge enterprise tier for: webhook-powered dynamic dropdowns that pull live data from your stack, decision-table approvals over email with per-row scheduling, and an MCP server that lets Claude or Codex build the form and the n8n workflow behind it. Pricing is also flat — Free, $49 Pro, $129 Business — with no per-response fees.
Does FormNode integrate with ConnectWise Manage?
Yes. FormNode forms can be embedded in the ConnectWise Manage Pod with the company ID auto-passed via {{Company.RecID}}. Org integration mappings store the ConnectWise Company ID per-client so it's automatically included in every webhook call you make to ConnectWise.
Does FormNode work with n8n?
Yes — FormNode is purpose-built for n8n. Point any select field at an n8n webhook to populate the dropdown, fire tracked submissions into n8n flows, run approvals as n8n callbacks, and use the official @joshuanode/n8n-nodes-formnode community node to manage forms and submissions from within n8n itself.
Can I host FormNode on my own domain?
Yes — Pro and Business plans include custom domain support. You CNAME forms.yourcompany.com to FormNode and verify with a TXT record. TLS is auto-provisioned via Cloudflare for SaaS. Customer portals and form submission URLs all serve under your domain.
What is the MCP server?
The Model Context Protocol server at mcp.formnode.io lets AI agents like Claude, Codex, or any MCP client build forms, manage clients, pull submissions, and run approvals in plain English. It ships on the Business plan and works with any tool that speaks MCP.
What happens to my data if FormNode shuts down?
FormNode publishes a written commitment — the No-Orphan Guarantee — that if the product is ever sunset, the codebase is released under AGPL-3.0 with a Docker image you can self-host and an importer for your exported data. Your submissions are always exportable on every plan, including the free tier. Read it at formnode.io/promise.
Is there a free plan?
Yes. The Starter plan is free forever and includes 3 active published forms, 500 submissions/month fair use, 5 organizations, 1 staff user, webhook-powered dynamic fields, email notifications, and inline embed. No credit card required.
Make FormNode the form layer for your IT automation stack.
Replace the generic form builder where it hurts first: onboarding, ticket intake, access requests, approvals, and any form that needs live data.