Ninja Forms

Pull Ninja Forms data out of WordPress: agents list a site's forms, read stored submissions, and retrieve individual entries to route captured leads into CRMs, spreadsheets, and notification tools.

4 actions Basic auth available

Ninja Forms website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A scheduled poll runs every ten minutes against the WordPress site's contact form

List Submissions pulls entries stored since the last processed post ID

Get Submission retrieves each entry's detail, and the agent maps meta fields back to labels using the form definition from List Forms

The agent scores each entry: real inquiry, spam, or ambiguous

Real inquiries upsert into the CRM with source form and timestamp attached

Ambiguous entries, a half-filled enterprise inquiry, a pricing question with a suspicious domain, go to a marketer who decides route, discard, or reply

A Slack digest summarizes the batch with counts and the held entries

What This Integration Enables

Ninja Forms is the workhorse form plugin on a lot of WordPress sites, and its entries too often retire quietly into the wp-admin database. FlowRunner turns that database into a source: agents call List Forms to map the site's forms, poll List Submissions for stored entries, and use Get Submission to pull individual records for routing and enrichment. There is an honest caveat here that this connector states plainly rather than hiding: Ninja Forms has no official public REST API. Reads go through the plugin's internal endpoint and the WordPress core REST API, which means the site must expose the submission post type in REST, and field values stored as post meta may need the form definition to interpret. FlowRunner's position is that a connector should tell you where the floor creaks, because an agent workflow built on undocumented behavior needs a human who knows that, and a verification step that proves the endpoints work on your install before the pipeline depends on them. - Poll a WordPress site's forms and route real inquiries into CRMs, sheets, and Slack without anyone logging into wp-admin - Retrieve a single entry by ID to enrich a downstream record with its original submission - Push data into a form with Submit Form to exercise the plugin's full processing pipeline, gated and experimental by design - Keep a person on the triage calls that scoring cannot settle - Archive entries outside WordPress so a site rebuild never takes the submission history with it

Without FlowRunner

Leads live in wp-admin Form entries accumulate inside the WordPress dashboard, and checking them means logging in and remembering to

Notification emails as a system of record The team forwards Ninja Forms emails to each other, and whether a lead got followed up depends on whose inbox it hit

Spam and signal mixed Real inquiries sit in the same list as bot submissions, and triage is a human scrolling

With FlowRunner

Entries pulled into the pipeline Agents poll List Submissions and route real inquiries into the CRM minutes after they arrive

One system of record Every entry lands in the CRM or the tracking sheet with its source form, timestamp, and triage decision recorded

Humans see only the ambiguous Agents file the obvious and discard the junk, and a person rules on the entries that could go either way

Use Case Scenarios

The contact form that feeds the CRM instead of an inbox

An agency's site runs its contact and audit-request forms on Ninja Forms. An agent polls List Submissions every ten minutes, resolves field meta against the form structure, and creates each real inquiry as a contact in [HubSpot](/integrations/hubspot) with the message body logged as a note. A [Slack](/integrations/slack) message tells the on-duty strategist a new audit request exists. The old workflow, a shared notifications@ inbox, is retired rather than replaced by a faster inbox.

The submission archive that survives the plugin

Compliance wants form entries retained outside WordPress. On a nightly schedule, the agent sweeps List Submissions, pulls each new entry with Get Submission, and appends the full record to [Google Sheets](/integrations/google-sheets) and the archive store, keyed by post ID so re-runs never duplicate. When the site gets rebuilt eighteen months later, the entry history is not a casualty of the migration.

Testing the form pipeline before the campaign lands

Before a launch drives traffic to a landing page, an ops engineer wants proof the form's notifications and save actions actually fire. A workflow uses Submit Form to push a clearly-labeled test entry through the plugin's real processing, then verifies the entry appears in List Submissions and the notification arrived. Because this endpoint is experimental and touches production, the workflow requires a human to approve each test run and names the target form in the approval request.

Human-in-Loop Highlight

Submit Form writes into a production WordPress site as if a visitor filled the form out, and everything downstream of it is real: the plugin runs validation, fires notification emails to whoever the form notifies, and executes every configured save action. There is no unsend. A misconfigured field map does not fail quietly in a log; it emails your sales team a malformed lead or triggers a Zapier hook someone forgot was attached. The endpoint is also heavily experimental, posting to the plugin's front-end AJAX handler that normally expects a browser nonce, so behavior must be verified against a real submission. FlowRunner treats every Submit Form call as a gated operation: the agent presents the target form, the exact field payload, and what the form's processing will trigger, and a person approves before anything posts. The read operations on this page run free. The one that makes a production site act does not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

4 actions

Forms

List Forms Lists the Ninja Forms forms on the connected WordPress site, returning each form's ID and title. Calls the plugin's internal endpoint, which is undocumented and version-dependent; requires a WordPress user with permission to manage Ninja Forms.

Submissions

List Submissions Lists stored form submissions via the WordPress core REST API, with pagination and full-text search. Returns results only if the site exposes the submission post type in REST; field values live in post meta and may not appear in the default response.
Get Submission Retrieves a single submission by its WordPress post ID. Same REST exposure requirement applies, and interpreting meta fields may require the form definition to map field IDs to labels.
Submit Form Submits data to a form as if a visitor filled it out, running the plugin's normal validation, notifications, and save actions. Heavily experimental: posts to the front-end AJAX handler and can fail nonce and spam checks. The operation this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Ninja Forms?

FlowRunner agents can run List Forms, List Submissions, and Get Submission in Ninja Forms, plus 1 more action.

Does connecting Ninja Forms to FlowRunner require OAuth?

No. Ninja Forms connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Ninja Forms trigger a FlowRunner workflow automatically?

Ninja Forms doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Ninja Forms

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us