✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Ninja Forms: submissions as customizable tables

Ninja Forms stores submissions as nf_sub posts with field values in postmeta. SleekView pivots them into a proper table with one row per submission and named columns per field.

♾️ Lifetime License available

SleekView table view for Ninja Forms

Postmeta is hidden — SleekView makes it readable

Ninja Forms doesn't use a custom nf_submissions table — submissions are stored as nf_sub posts with field values stored as _field_<id> rows in postmeta. SleekView pivots that postmeta into proper columns, so a submission is one row with named fields instead of a JSON-like dump.

Sample columns

A typical Ninja Forms submissions view

Pivots postmeta rows starting with _field_ into named columns based on the form's field definitions.
Source: wp_posts (nf_sub) + wp_postmeta
Sub # Form ID Submitted Email Subject
#412 3 Apr 24 alex@studio.co Demo request
#411 3 Apr 24 ria@design.io Pricing question
#410 5 Apr 23 tom@hello.dev Newsletter
#409 3 Apr 23 mia@brew.coop Demo request

Comparison

Default Ninja Forms admin vs SleekView

Default Ninja Forms admin

  • Submissions are nf_sub custom posts — postmeta values aren't shown by default
  • Per-field values stored as _field_<id> rows are unreadable without code
  • Cross-form submissions list requires custom code or exporters
  • Bulk operations are limited to standard WP-Posts actions
  • Filtering by form + date + a specific field value at once isn't built in

SleekView

  • Pivot _field_* postmeta into named columns
  • Cross-form submissions in one view with _form_id as a column
  • Inline-edit submission values without dropping into a per-post screen
  • Filter by form ID + date + arbitrary field values together
  • Save view sets per role (e.g. "Demo requests, last 7 days")

Features

What SleekView gives you for Ninja Forms

Postmeta becomes columns

_field_<id> postmeta rows pivot into named columns at query time. Each form's field labels become the column headers.

Filters that don't exist by default

Filter by _form_id, post_date range, and pivoted field values — saved as named views your team can reuse.

Inline edit & delete

Update field values, mark submissions, and delete spam directly from the row — no per-post round trip.

Audience

Who uses SleekView for Ninja Forms

Sales & support

All form leads in one cross-form table, filtered to the last 7 days, with email and subject visible.

Spam moderation

Filter and bulk-delete spam-flagged submissions across forms in one pass.

Form auditors

See submission counts per form and per day — answer "which form is performing?" without code.

Questions

Common questions about SleekView for Ninja Forms

No — Ninja Forms 3.x stores submissions as nf_sub custom posts. Per-field values live in postmeta as _field_<id> rows, with the form ID stored as _form_id. SleekView reads both and pivots them into a proper tabular view.

 

Yes — SleekView writes back to postmeta, with conflict detection and audit logging.

 

SleekView reads the form's field definitions to map _field_<id> keys to human-readable labels. You don't have to maintain a column-key mapping by hand.

 

Add-ons that store extra data in postmeta on the same nf_sub post (Stripe, MailChimp, file uploads) are visible as additional pivotable columns.

 

Ninja Forms exports work as before — SleekView is read/edit only and doesn't touch how Ninja Forms exports CSV/JSON.

 

Yes — deleting a submission row trashes the nf_sub post (and its postmeta), same behaviour as the default WP admin.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView