Do I need the community node to receive form submissions in n8n?

No. A normal n8n webhook is enough to receive FormNode submissions and dynamic dropdown option requests. The community node is for workflow steps that need authenticated access back into FormNode.

Which FormNode plan includes the n8n community node?

The official n8n community node is included with the Business plan, alongside the MCP server, REST API, white-label controls, email template editor, and webhook delivery tracking.

FormNode n8n community node

Q: What is the FormNode n8n community node?

The FormNode n8n community node is the official n8n package for working with FormNode resources from inside n8n. Use it when a workflow should read or manage forms, organizations, submissions, or approvals through FormNode's API instead of only receiving a webhook.

Install @joshuanode/n8n-nodes-formnode when an n8n workflow needs to call FormNode as an authenticated system, not just receive a form submission. Webhooks are still the right path for most form starts and dynamic dropdown option lookups.

Direct answerUse the FormNode n8n community node for authenticated FormNode API work inside n8n. Use normal n8n webhooks when FormNode needs to send a submission, approval callback, or read-only dynamic-field request into n8n.

When to use the community node

An n8n workflow needs to list or inspect FormNode resources.
A workflow should create, update, or cancel a FormNode approval.
A workflow needs to pull submission records after an external event.
You want FormNode API credentials managed as n8n credentials instead of custom HTTP headers in every node.
The workflow is part of a Business-plan setup that also uses the REST API or MCP server.

When a webhook is enough

A FormNode form submits into n8n to start a workflow.
A dynamic dropdown needs n8n to return option JSON.
An approval callback only needs to resume or branch a workflow.
You do not need n8n to read or mutate FormNode records after the event arrives.

Install the package

In n8n environments that allow community nodes, install the package name:

@joshuanode/n8n-nodes-formnode

For self-hosted n8n, use the normal community-node install path for your deployment. In managed n8n environments, confirm that community nodes are enabled for your workspace before planning around this node.

Create a FormNode API key

Open FormNode Settings and create a dedicated API key for n8n.
Give the key only the access your workflow needs.
Store the key in n8n credentials, not in workflow code, form copy, or public docs.
Use one key per n8n instance so it can be revoked without breaking unrelated automations.

Common workflow patterns

Pattern	Best interface	Reason
Receive a submitted form	n8n Webhook Trigger	FormNode already sends the final payload to the configured webhook.
Load dynamic dropdown options	n8n Webhook Trigger	The endpoint should be read-only and return option JSON quickly.
Create or manage an approval	FormNode community node	n8n is calling FormNode as an authenticated API client.
Fetch submission records later	FormNode community node or REST API	The workflow needs authenticated access back into FormNode.
Let an AI agent build the form	FormNode MCP server	MCP is the agent control surface; n8n remains the workflow runtime.

Production notes

Keep dynamic dropdown endpoints read-only. Do not create users, tickets, or approvals from an option lookup.
Use stable field keys in FormNode so n8n workflows do not break when labels change.
Use FormNode submission IDs or idempotency keys when retries could duplicate downstream work.
Keep FormNode API keys in n8n credentials and rotate them independently from MCP keys.
Use webhook delivery tracking for final submissions when the workflow is customer-facing or operationally sensitive.

Related docs

FAQ

What is the FormNode n8n community node?

It is the official n8n package for authenticated FormNode API work from inside n8n. Install @joshuanode/n8n-nodes-formnode in n8n environments that allow community nodes.

Do I need it for basic n8n forms?

No. Basic submission and dynamic dropdown workflows can use normal n8n webhooks. Add the community node when the workflow needs to call back into FormNode as a client.