When form submission is received in Ninja Forms, send the submission details to n8n.io

Every Ninja Forms submission on your WordPress site is passed to n8n.io with its field values, so an n8n workflow you already run can take the entry from there and handle the rest.

Ninja Forms

n8n.io

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.9k sites Free to import

The When form submission is received in Ninja Forms, send the submission details to n8n.io workflow on the FlowMattic canvas, with 2 steps across Ninja Forms, n8n.io — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

You may already run your larger automations in n8n.io, but your forms live on a WordPress site built with Ninja Forms. Getting each entry across usually means custom code or a plugin that posts to a URL. This workflow does the hand-off for you, with no code on your site.

The Ninja Forms trigger runs each time a visitor submits a form. FlowMattic collects the submitted values and passes them to the n8n.io Submit Data step, which sends them to the n8n workflow you point it at. From that moment n8n owns the data: it can route the entry, enrich it or write it to any tool your n8n workflow connects to.

The template has two steps and no conditions, so every submission of the form you pick is sent once. The n8n side needs a workflow that can accept incoming data, which in n8n means one that starts with a Webhook node. Task History in FlowMattic records each run, so you can see what left your site and what n8n answered.

Keep one automation hub in n8n

Your team builds every flow in n8n, and the WordPress contact form is the one source still outside it. This template feeds those entries into the same n8n workflows as your other lead sources.

Hand quote requests to a self-hosted stack

A Ninja Forms quote form passes each request to a self-hosted n8n instance, which writes it to your internal database and alerts the right person.

Split work between WordPress and n8n

FlowMattic handles the form capture on your site, and n8n takes on the longer multi-step processing you have already built there.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Ninja Forms New Form Submission
Runs each time a visitor submits the Ninja Forms form you choose. Each answer in the submission becomes a value you can map into the n8n.io step.
Step 2Action
n8n.io Submit Data
Sends the mapped submission values to n8n.io. Set the step up to reach the n8n workflow that should receive them, map the form fields you want to pass, and run a test to confirm the data arrives in n8n.

What you need

FlowMatticCore
Ninja Forms PluginPlugin
n8n.io AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Build and activate the receiving n8n workflow before you turn this one on. Start it with a Webhook node so it has somewhere to accept the data, then submit a test entry and check that it shows up there.
Add a Filter after the Ninja Forms trigger if only some entries should reach n8n, for example when a consent checkbox is ticked or a service dropdown has a certain value.
Submit one test entry that fills every field, then open the run in n8n and check how the values arrived. Build the later n8n nodes from what you see there, not from the field labels on the form.

Questions about this workflow

Do I need anything in n8n.io before importing this Ninja Forms workflow?

Yes. You need an n8n workflow that can take in outside data, which in n8n means one that starts with a Webhook node. This template only sends the data; what happens to it after that is decided in n8n.

Does every Ninja Forms entry go to n8n, or only some?

Every submission of the form you pick on the trigger is sent, because the template has no conditions. Add a Filter after the trigger to send only the entries you want.

What happens if n8n is down when someone submits the Ninja Forms form?

The Submit Data step returns an error for that run, and Task History shows it on the step. Ninja Forms still handles the entry as it normally would, since the workflow only reads the submission.

Can n8n send data back to FlowMattic?

It can, through a second workflow. FlowMattic's n8n.io app also has a Receive Data trigger, so an n8n workflow can start a FlowMattic workflow on your WordPress site.