Resources · Make integration

NinjaForms Make integrationAutomate NinjaForms with Make.

What happens to a form entry after someone clicks Submit on your WordPress site? The NinjaForms Make integration gives you 1 instant trigger that hands each new submission to Make. This guide shows how to connect your account and build a first scenario around it.

Try the NinjaForms integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the NinjaForms Make integration do?

The NinjaForms Make integration picks up every new submission of a form built with the Ninja Forms WordPress plugin and passes what the visitor typed to a Make scenario, the automation you build in Make. From there, other apps take over: a spreadsheet, a CRM, an inbox.

Everything starts with one module, Watch New Form Submissions. A module is one brick of a scenario, and this one is an instant trigger: NinjaForms calls Make through a webhook as soon as a visitor submits the form. What happens next depends on the bricks you add from other apps.

A few typical setups. A quote request lands on your site and becomes a new row in a table your sales team already reads, much like the flows on the Airtable Make integration page. A support form turns into a ticket in your help desk, with the visitor's message copied over. A registration form for a workshop feeds a contact list, so nobody retypes names from the WordPress dashboard.

Know the limits before you start. The app has a single trigger and no action: Make cannot create, edit or delete forms or entries in NinjaForms. It has no Make an API Call module either, so what the trigger sends is what you get. The Make documentation also asks for a paid Ninja Forms account and admin access to the WordPress site.

NinjaForms may also exist as a node in n8n. If you are weighing both tools, the n8n vs Make comparison lays out the criteria, and our Make training covers the editor from the ground up.

Connect

How do you connect NinjaForms to Make?

  1. 01

    Add the trigger and open the connection

    In a new scenario, add the Watch New Form Submissions module and click Create a connection. A connection is your NinjaForms account linked to Make once, then reused by the module every time it runs.

  2. 02

    Name it if you run several sites

    The name field is optional. It pays off when you manage more than one WordPress site: a label with the site's name tells you at a glance which forms a scenario listens to.

  3. 03

    Authorize Make and save

    Follow what the window asks for: approve access on the NinjaForms side, or paste the key your account gives you. Click Save, and the connection appears in the module, ready for the next setting.

First scenario

Build your first scenario with NinjaForms

GoalWhen a visitor submits a NinjaForms form, Make sends the answers to the next tool of your choice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle becomes your first module.

  2. 02

    Pick the NinjaForms trigger

    Type NinjaForms in the search box, choose Watch New Form Submissions, then select or create your connection. Fill in the fields the module shows; Make lists what it can read once the account is linked.

  3. 03

    Add the destination

    Click the + on the right of the trigger and add a module from another app, a sheet or a CRM for instance. Map the form answers into its fields by picking them from the trigger's output.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry on your site. Each module shows the bundle it received, a bundle being one item passed along, here one submission. Check the answers landed where you expected.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, Make does not wait for a schedule: each new submission starts a run on its own, and every module run counts as one operation on your plan.

Triggers

What starts a NinjaForms scenario

1 module starts a scenario when something happens in NinjaForms. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by NinjaForms as soon as it happens.

NinjaForms1Watch New Form Submissions

Watch New Form Submissions

Instant trigger

In Make“Receives all data user fills in the form”

This trigger hands Make everything a visitor typed into your form the moment the entry is sent, so the answers reach your other tools without anyone copying them out of WordPress.

How it fires
instant, NinjaForms calls Make through a webhook as soon as a submission comes in.
When to use it
a contact or quote form whose entries should reach your sales pipeline while the lead is still warm.
Watch out
it is the only NinjaForms module in Make, so any follow-up step, such as a reply or a record update, has to come from another app in the scenario.
Need help

Need help automating NinjaForms with Make?

A person reads every message.

FAQ

NinjaForms and Make: common questions

01Is the NinjaForms Make integration free?
Yes, on the Make side. NinjaForms is a standard app, so it works from the Free plan, which allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the active scenario cap and allow runs of up to 40 minutes. Usage is counted in operations, one per module run. The Ninja Forms side is different: Make's documentation asks for a paid Ninja Forms account.
02What is needed to connect NinjaForms to Make?
Three things, according to Make's documentation: a paid Ninja Forms account, a WordPress site with the plugin installed, and an administrator account on that site. Once those are in place, add the Watch New Form Submissions module, click Create a connection, authorize Make or paste the key requested, and save. The connection is then reused by every NinjaForms module, which here means the single trigger. If the window asks for something you do not have, check the plugin license first.
03Does the NinjaForms trigger in Make fire in real time?
Yes. Watch New Form Submissions is an instant trigger: NinjaForms calls Make through a webhook as soon as someone submits a form, and the scenario starts right away. There is no polling interval to set, unlike scheduled triggers, which Make checks every 15 minutes by default. For testing, click Run once in the editor, then send a test entry from your site and read the bundle the trigger received. Nothing needs to be scheduled on your side.
04What can be done when a NinjaForms module is missing in Make?
It depends on the need. The NinjaForms app in Make has one trigger and no action, and it offers no Make an API Call module, so nothing on the NinjaForms side can be edited from a scenario. Anything after the submission is handled by other apps: a sheet, a CRM, a mailing tool, a help desk. If a case still needs custom work, the Make agency team can look at it with you.
05Should NinjaForms be automated with Make or n8n?
It depends on the tool your team already runs. Make offers NinjaForms as a standard app with one instant trigger, available from the Free plan, and a visual editor where you test with Run once. The same plugin often has a node in n8n too. Compare what each tool gives you for this app and for the apps that receive the data, rather than picking by name. The comparison page on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations