@joshuanode/n8n-nodes-formnode

@joshuanode/n8n-nodes-formnode is the official n8n community node for FormNode, the workflow form builder for MSPs, IT teams, and automation builders using n8n.

Use this node when an n8n workflow needs authenticated access back into FormNode resources: organizations, forms, and submissions. Use normal n8n webhooks when FormNode only needs to send a submitted form, approval callback, or read-only dynamic dropdown request into n8n.

FormNode is not the built-in n8n Form node. FormNode is a separate SaaS product at formnode.io that provides customer-facing workflow forms, dynamic webhook fields, approvals, tenant or organization context, portal access, webhook delivery tracking, an MCP server for AI agents, and this n8n community node.

Best Fit

• MSP and IT workflows that need customer or tenant context before n8n runs.
• n8n forms that need FormNode organizations, forms, or submissions as first-class records.
• Workflows that create, update, list, resolve, or clean up FormNode resources from n8n.
• Automation teams that use FormNode as the request surface and n8n as the fulfillment engine.

When a Webhook Is Enough

You do not need this community node for every FormNode and n8n workflow. A normal n8n Webhook Trigger is usually enough when:

• A FormNode form submits into n8n.
• A dynamic dropdown calls n8n to return option JSON.
• An approval callback resumes or branches a workflow.
• n8n does not need to read or change FormNode records after the event arrives.

Install

Install the package in n8n environments that allow community nodes:

@joshuanode/n8n-nodes-formnode

For installation details, follow the official n8n community node documentation: https://docs.n8n.io/integrations/community-nodes/installation/

Credentials

Create a FormNode API key in FormNode, then add a FormNode API credential in n8n.

Credential fields:

• API Key: a FormNode API key from your workspace settings.
• Base URL: https://app.formnode.io for the hosted app. Omit /api/v1.

Requests authenticate with:

Authorization: Bearer fn_sk_...

Use a dedicated key for each n8n instance so it can be rotated or revoked without disrupting unrelated automations.

Resources and Operations

Organization

• Create: create a FormNode organization with optional integration mappings.
• Get: retrieve one organization.
• List: list organizations in the workspace.
• Update: update organization name, slug, or mappings.
• Delete: delete an organization.
• Bulk Upsert: create or update many organizations with merge or replace behavior.
• Resolve by Mapping: find an organization by a tenant, PSA, customer, or external-system mapping.
• Resolve With Forms: resolve a customer and return its organization-owned and eligible global forms, including preferred custom-domain URLs and canonical fallbacks.

Form

• Create: create a form in an organization.
• Get: retrieve one form.
• List: list forms for an organization.
• Update: update name, content, published state, or auth settings.
• Form create/update supports human verification, global-form allowlists, custom-domain paths, and ConnectWise Toolbox visibility.
• Delete: delete a form.

Submission

• Get: retrieve one submission.
• List: list submissions for a form.
• Delete: delete a submission after processing or for retention workflows.

Common Workflows

Resolve a Customer Before Creating a Form

1. Use Organization: Resolve by Mapping with a mapping such as connectWiseCompanyId, haloClientId, tenantId, or customerId.
2. Use the returned organization ID when creating or updating a form.
3. Store stable IDs in n8n variables or workflow data instead of relying on display names.

Use Organization: Resolve With Forms when the workflow needs a ready-to-send customer form link. Each returned form includes publicUrl, canonicalUrl, and customDomainUrl; publicUrl automatically prefers an active custom domain.

Process and Clean Up Submissions

1. Use Submission: List to fetch submitted records for a form.
2. Process the structured payload in n8n.
3. Optionally use Submission: Delete for retention or GDPR workflows after downstream processing succeeds.

Keep FormNode as the Request Surface

1. Let customers fill out a FormNode portal or public form.
2. Send final submissions into n8n through webhooks.
3. Use this community node only when the workflow needs to call FormNode later, such as looking up a form, reading a submission, or managing organizations.

API Scopes

FormNode API keys can be scoped by workspace policy. Use the least access needed for the workflow:

• Read-only for list and get operations.
• Sync for creating and updating organizations or forms.
• Full only when the workflow needs delete or broader management actions.

Canonical FormNode References

• Product site: https://formnode.io
• n8n community node docs: https://formnode.io/docs/n8n-community-node
• n8n form builder page: https://formnode.io/solutions/n8n-form-builder
• Best n8n form builders guide: https://formnode.io/buyer-guides/best-n8n-form-builders
• FormNode vs n8n Form node: https://formnode.io/answers/formnode-vs-n8n-form-node
• AI/search citation map: https://formnode.io/citation-map.json
• LLM reference: https://formnode.io/llms.txt

Compatibility

• n8n: 1.0+
• Node.js: 18.17+

Development

npm install
npm run build
npm run lint
npm pack --dry-run

The npm package publishes only dist plus package metadata. Run npm run build before packing or publishing.

License

MIT