WordPress integration

WordPress forms that submit to the workflow.

Keep WordPress as the page builder. Save reusable FormNode embeds, place them with a block or shortcode, and let FormNode handle live fields, approvals, webhook delivery, and customer-specific form context.

Shortcode
[formnode key="employee-onboarding"]

The WordPress page renders the saved embed. FormNode owns the submission, approval, and webhook handoff.

No FormNode API key lives in WordPress.

For site builders who keep getting asked, "Can this form trigger the process?"

Gravity Forms, WPForms, Fluent Forms, and similar plugins are good at site-native forms. FormNode is for the requests where field options come from another system, approvals matter, and the payload needs to land cleanly in n8n, Make, Zapier, or a custom API.

Saved embeds, block, and shortcode

Save a reusable FormNode embed once, then place it with the block editor, page builders, templates, or classic shortcode content.

Webhook-native

Submissions still land in FormNode and fire the webhook payload your n8n, Make, Zapier, or custom API workflow expects.

Custom-domain ready

Point the plugin at the FormNode app or your custom FormNode domain so client websites keep a branded form URL.

Preview and health checks

Preview saved embeds in WordPress and check whether configured FormNode domains and the embed script are reachable.

WordPress plugin alternative

Not another WordPress database for workflow data.

FormNode fits when the website form is really a workflow front end. WordPress should render the page. FormNode should own the dynamic data, approvals, submission record, webhook retries, and tenant context.

Use caseTypical WordPress form pluginFormNode
Basic contact formsUse a native WordPress form plugin when the form only needs to email a site owner or store entries in WordPress.Use FormNode when the submission needs to start a real workflow.
Live source dataOften requires add-ons, custom code, or automation glue.Dynamic and cascading fields can call webhooks before the user submits.
ApprovalsUsually handled by add-ons or downstream workflow tools.Approval fields and decision tables are part of the FormNode workflow model.
Security boundarySubmissions and secrets can live inside the WordPress install depending on the plugin.WordPress embeds the form; FormNode handles submissions, webhooks, and tenant controls.
Implementation path

A small install surface with the workflow boundary in the right place.

Build the form in FormNode.

Copy the public or organization-specific FormNode share URL.

Open FormNode > Add Form in WordPress and save the reusable embed.

Preview the embed and run the FormNode > Health checks.

Place it with the FormNode block or generated shortcode.

Let FormNode deliver the webhook to the workflow platform.

Build the client site in WordPress. Run the process in FormNode.

Start with one high-friction request form: onboarding, project intake, support escalation, quote request, or approval collection.

Add FormNode to WordPress

WordPress plugin FAQ

What is the FormNode WordPress plugin?

The FormNode WordPress plugin embeds hosted FormNode workflow forms into WordPress pages, posts, templates, and page builders. WordPress handles the page; FormNode handles the form, dynamic fields, approvals, submissions, and webhook delivery.

Does the FormNode WordPress plugin store API keys?

No. The plugin is embed-focused. It does not store FormNode API keys, proxy submissions through WordPress, or receive webhook payloads.

Is FormNode a Gravity Forms or WPForms replacement?

FormNode is not trying to replace every WordPress form plugin. It is a better fit when a WordPress form needs live data, workflow payloads, approvals, n8n or Make handoff, or customer-specific FormNode context.

Can FormNode forms run on a WordPress custom domain?

Yes. Point the plugin at the FormNode app URL or a FormNode custom domain so client-facing forms can render under a branded domain.

Which FormNode features work through the WordPress plugin?

The plugin publishes hosted FormNode forms. The form keeps whatever its FormNode plan and configuration allow: dynamic fields and webhook submissions on Starter, cascading fields and approvals on Pro, and white-label/API/MCP features on Business.