✨ 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 Kanban for Forminator

SleekView reads your Forminator form, quiz, and poll submissions directly from the entry tables, groups them by entry state or any field you nominate, and lets your team drag each card between columns to move triage forward without opening the default Forminator submissions list view.

♾️ Lifetime License available

SleekView Kanban board for Forminator

Why Forminator submissions need a board on top

Forminator stores submissions in wp_frmt_form_entry with values broken out to wp_frmt_form_entry_meta, keyed by form ID and entry type which can be custom-forms, quizzes, or polls. There is no built-in status field beyond entry_type and is_spam, which means the default admin shows a paginated table with very few signals about what stage each submission is in.

SleekView reads the same wp_frmt_form_entry table, joins meta for whatever fields you put on the card face, and surfaces every form field as a possible grouping axis. The natural starting point is is_spam combined with a custom Stage dropdown you add to the form, because Forminator does not ship with multi-state workflow tracking out of the box. Hidden admin-only fields work great for this.

Dragging a card between columns updates the entry meta through Forminator own entry update API and fires the standard entry hooks so any Zapier feeds, Slack notifications, or email integrations wired to entry changes run exactly as they would from the admin. Spam entries are filtered out by default but available through a dedicated spam review board for moderators.

Workflow

From Forminator submissions to a board in four steps

1

Connect Forminator

Pick the Forminator form, quiz, or poll to visualize from the SleekView source picker. Every field defined in the Forminator builder, including hidden admin fields and integration meta written by Zapier, Slack, or webhooks, is auto-detected as a possible card field or grouping axis.
2

Pick the column to group by

Choose any field as your grouping key. Forminator has no built-in workflow status, so most teams add a custom Stage dropdown to the form, hide it from the public view, and group on that. The is_spam flag is also a valid axis for spam moderation boards.
3

Choose what shows on cards

Drag up to six fields onto the card face. Common picks are name, email, subject line, payment amount when the Stripe or PayPal field is used, and submission date. Cards stay compact at a glance and expand on click to reveal every field stored on the entry record.
4

Enable drag and drop

Flip on write-back so each card drag calls the Forminator entry update API, persisting the new meta value and firing the standard entry hooks. Any Zapier feeds, Slack notifications, or webhook integrations wired to entry changes run exactly as if the update came from the admin.

Sample board

Sample Forminator triage board

A live preview of a contact form board grouped by custom Stage field, with submitter name and subject on each card and per-column counts visible in the header for instant context.
New
38
Quote request from agency lead
Mila Petrova, 1h ago
Demo question on team plan
Ahmed Yusuf, 2h ago
Integration with Slack ask
Lara Costa, 3h ago
In review
19
Refund query for invoice 5512
Joel Reyes, assigned
Bug report on payment step
Mei Tanaka, assigned
Press inquiry from podcast
Stefan Werner, assigned
Closed
96
Onboarding scheduled for next week
Closed today
Quote sent to legal team
Closed yesterday
Refund processed via Stripe
Closed today
Spam
10
Crypto promo from anonymous
Flagged by Akismet
SEO outreach blast
Marked spam by admin
Bot signup with random text
Auto flagged today

Comparison

Default Forminator submissions versus SleekView Kanban

Default Forminator submissions

  • Submissions show as a paginated table with no built-in workflow status beyond spam flag
  • Status changes require opening each entry individually, no bulk drag between states
  • Custom dropdown fields cannot become the grouping axis from the default submissions screen
  • There is no concept of a multi-stage workflow without writing custom code or add-ons
  • Team handoffs rely on internal notes invisible from the default submissions list view

SleekView Kanban

  • Reads directly from wp_frmt_form_entry and entry meta with no duplicate storage
  • Drag-and-drop writes back through the Forminator entry update API to keep state in sync
  • Group by is_spam or any custom Stage dropdown field added to the form
  • Card face accepts up to six fields including totals from the Stripe or PayPal field
  • Works with Zapier, Slack, and webhook integrations without breaking their entry hooks

Features

What SleekView Kanban gives you for Forminator

Group by any field on the form

Forminator has no built-in workflow status so any dropdown, radio, or checkbox field on the form is a valid grouping axis. Add a hidden admin-only Stage dropdown to your form once and any board can group on it to model your real workflow stages.

Drag-and-drop writes back to entries

Moving a card calls the Forminator entry update API, which persists the new meta value to wp_frmt_form_entry_meta and fires the standard entry hooks so Zapier feeds, Slack notifications, and webhook integrations wired to entry updates continue to run exactly as before.

Per-role column visibility

Hide the Spam column from sales reps, hide In Review from public-facing roles, or expose admin-only columns to moderators. Permission rules read from the standard WordPress role and capability map you already configured for Forminator submission access.

Audience

Common Forminator boards teams build

Contact form triage

Group inbound contact submissions by a custom Stage dropdown so support sees what is waiting, what is in progress, and what was closed yesterday at a glance instead of scrolling the default submissions table.

Quiz response review

Group quiz submissions by score band or by a custom reviewer Stage so the team can decide which respondents to follow up with, which to invite to interviews, and which to thank politely.

Poll moderation

Group poll responses by a custom Moderation Stage so the team can review free-text answers, approve them for public display, or hide spam responses before the published results page refreshes.

The bigger picture

Why a board beats the default Forminator list view

Forminator handles forms, quizzes, and polls in one plugin but its admin assumes you will read submissions one at a time. That assumption holds for a basic contact form and breaks down the moment a form becomes part of a workflow with multiple stages and multiple teammates handling triage at the same time. A kanban board fills the missing layer: queue visibility.

You see at a glance how many submissions are sitting in each stage, which ones have been waiting the longest, and what the team closed since yesterday. Status changes happen with a single drag instead of opening each entry edit screen, which compounds into real time savings once volume picks up. Because every column maps back to a real field on the entry, the board is not a parallel system that drifts.

Everything you see is exactly what Zapier, Slack, and your other integrations already read from the same Forminator entry table. New teammates onboard in minutes because the board itself documents the workflow visually. The result is a Forminator admin that finally matches how operations, marketing, and moderation teams actually run their day.

Questions

Common questions about SleekView Kanban for Forminator

The drag calls the Forminator entry update API, which persists the new meta value to wp_frmt_form_entry_meta and fires the standard entry update hooks. Any Zapier feed, Slack notification, or webhook integration wired to entry updates runs exactly as if the change had come from the standard admin submissions screen.

 

The recommended pattern is to add a hidden admin-only Stage dropdown field to the form with options like New, In Review, and Closed. SleekView treats that field as the grouping axis and you get a real workflow board on top of submissions that originally only had a single received state.

 

Yes. Quizzes and polls are stored in the same wp_frmt_form_entry table with a different entry_type. SleekView treats them the same way and you can build boards on top of quiz submissions grouped by score band or poll responses grouped by a custom Moderation Stage field.

 

When a Stripe or PayPal field is used, payment status is written to the entry meta. SleekView surfaces that as a groupable axis, so you can build a board with Pending, Paid, Failed, and Refunded columns reading directly from the payment field meta on each entry row.

 

Yes. Boards are saved as named views and each view scopes to specific WordPress roles. Sales reps can see a pipeline board, support can see a triage board, and moderators can see a spam review board, all reading from the same underlying Forminator entry table.

 

Yes. Any submission stored in wp_frmt_form_entry with the right form ID appears on the board regardless of how it was created. Submissions pushed in via Zapier or other automation tools using the Forminator entry endpoints are indistinguishable from native form fills.

 

Yes. The same role and capability rules that gate the default Forminator submissions screen also gate SleekView. A user who cannot view submissions in the standard admin cannot view them on the board, and read-only roles get a board they cannot drag cards on.

 

Spam-flagged submissions have is_spam set to one and are filtered out of every board by default so they do not pollute triage. A dedicated Spam review board can be built that flips that filter to surface only spam-flagged entries for moderator review and recovery.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...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