✨ 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 AI Power

SleekView Kanban groups AI Power bulk generation runs into status lanes inside the WordPress admin, so editors can drag cards from queued through generating, draft, and live without opening each run, clicking a status dropdown, and saving one row at a time.

♾️ Lifetime License available

SleekView Kanban board for AI Power

Why bulk AI Power runs need a board

AI Power's bulk content generator can spin up hundreds of articles in a single run. Each row in the runs table carries a run_status, a target post_type, the source prompt template, and timestamps for queued, started, and completed. The plugin's own admin lists those runs as a flat WordPress table that sorts by created time. That table is the right idea at a small scale and the wrong shape once a publisher has dozens of runs sitting in different lifecycle stages.

SleekView Kanban reads the same wp_aipower_runs rows and groups them by run_status, which is the obvious pipeline column for AI Power. Each card surfaces the target post type, prompt template name, model used, and the count of generated drafts inside the run, so editors can see exactly which runs are still mid-generation and which are blocked on a human review without clicking into anything. A small badge on the card flags any run that hit an OpenAI error during generation.

Dragging a card from review into live writes the new run_status back to the AI Power runs table, so the plugin's own bulk publish action picks up the change on its next cron pass and pushes the generated drafts live. Cards that move into rejected drop the linked drafts into trash, and a confirmation modal prevents a misclick from publishing or trashing a multi-thousand-word batch by accident.

Workflow

Connect AI Power to SleekView

1

Select AI Power in SleekView

Inside SleekView, pick AI Power from the data source list. SleekView introspects the runs table, the linked drafts table, and every meta key AI Power stores per run, so you do not need to write any SQL or fill in a field mapping form before building the board.
2

Group by run_status

Set run_status as the group-by field. SleekView reads every distinct value AI Power uses, including queued, generating, draft, live, and failed, and turns each one into its own lane with a row count, so the board mirrors the actual pipeline rather than a generic backlog metaphor.
3

Pick which fields show on cards

Cards usually carry the prompt template name, the target post type, the OpenAI model, and the draft count. Everything else stays searchable inside the card detail panel, so an editor can still pull up the full prompt, the temperature setting, or the run owner when they need it.
4

Turn on writable kanban mode

Flip the drag-and-drop switch and SleekView writes status changes back to the AI Power runs table. Drops respect WordPress capabilities, so junior staff can drag from queued to draft but only an editor with publish_posts can promote a run to live or move it into rejected.

Sample board

Sample AI Power bulk runs board

AI Power bulk runs grouped by run_status, with card fronts showing prompt template, target post type, and draft count across queued, generating, draft, and live.
Queued
14
March Listicle Batch for Outdoor Gear
template: listicle, 40 drafts
Buying Guides for Smart Home Devices
template: buying-guide, 32 drafts
How-To Posts for Beginner Cooks
template: how-to, 28 drafts
Generating
4
Comparison Posts for Mechanical Keyboards
started 6m ago, 22 of 30
Local SEO Pages for Plumbing Niche
started 9m ago, 18 of 26
Round-Up Posts for Coffee Subscriptions
started 12m ago, 11 of 20
Draft
27
Beginner Yoga Guide Batch
24 drafts, awaiting editor
Sourdough Recipe Series
18 drafts, awaiting editor
Home Studio Setup Guides
22 drafts, awaiting editor
Live
96
January Affiliate Listicle Batch
42 posts live, 86 percent CTR
Best Of 2025 Round Up Series
30 posts live, 71 percent CTR
Holiday Gift Guide Batch
26 posts live, 92 percent CTR

Comparison

Default AI Power list vs SleekView Kanban

Default AI Power runs list

  • Flat runs table that sorts only by created time and current status badge
  • No view of how many drafts inside a run are still generating or already done
  • Status changes require opening a run, scrolling to a dropdown, and saving
  • Bulk actions cap at delete, with no way to promote many runs to live at once
  • Failed runs share the same table styling as healthy ones and hide in long lists

SleekView Kanban

  • Groups AI Power runs by run_status with live counts next to each lane
  • Drag a card between lanes to write status back to the AI Power runs table
  • Card fronts surface template, target post type, model, and draft count
  • A confirmation modal protects bulk publish and bulk trash moves on large runs
  • Failed runs sit in their own clearly colored lane for retry triage

Features

What SleekView Kanban gives you for AI Power

One card per AI Power run

SleekView treats each AI Power run as a single card on the board, so a thousand drafts grouped into thirty runs feels like a manageable thirty-card view. Editors expand the card to inspect the drafts inside, but the day-to-day pipeline view stays at the run level where decisions happen.

Drag updates run_status

Dropping a card on a new lane writes the new run_status back to the AI Power runs table, so the next cron tick picks up the change and triggers any bulk publish or bulk trash action AI Power already supports. The behavior matches the plugin's own dropdown exactly.

Bulk action safety modal

Moves that affect many WordPress posts at once, like dragging a forty-draft run from draft to live, pop a confirmation modal that lists the post count and the destination lane. A single keyboard shortcut confirms the move, so the safety net never gets in the way of fast editors.

Audience

Where AI Power teams reach for the board

Affiliate publishers at scale

Large affiliate sites schedule recurring bulk runs and use the board to see how many draft batches need editor review before the next publish window. The draft lane becomes the editor's working queue without any custom code.

Agencies producing for clients

Agencies running AI Power for several clients use one board per client. Filters scope the view to the right post type and prompt template, so two account managers can work on their own clients side by side without seeing each other's drafts.

Operators triaging failed runs

Operators monitor the failed lane to catch OpenAI rate limit errors, prompt size overruns, or model deprecations. Dragging a failed run back to queued retries the entire batch with one motion instead of editing each row by hand.

The bigger picture

Why a board fits AI Power's bulk model

AI Power's strongest feature is that it can generate hundreds of posts in one run. That strength turns into a weakness on the admin side, because hundreds of posts produce hundreds of rows in any default list, and important decisions hide inside the noise. A kanban shifts the unit of inspection from the single post back up to the run, which is the level where editors actually make decisions.

A whole batch is either ready for review or not, a whole batch either ships or not, and the board treats it that way. The drag gesture is faster than any dropdown, the count badges remove any need for a spreadsheet to track progress, and the failed lane keeps OpenAI errors visible instead of buried. The plugin still does the generation.

The board makes the human review match the scale of the generator.

Questions

Common questions about SleekView Kanban for AI Power

SleekView reads the standard AI Power database tables, which exist in both the free and premium builds. The kanban renders the same way regardless of license, so you can start on free, prove the workflow inside one editorial team, and upgrade AI Power independently when you need its premium generation features.

 

Yes, but the move is gated by a confirmation modal that shows the destination lane and the exact count of WordPress posts that will become published. AI Power's own bulk publish action picks up the run_status change on its next cron tick and pushes every draft inside the run to live in a single batch.

 

Yes. Each board accepts saved filters per user, so an editor can scope their view to a single prompt template, a single target post type, or a single model. The kanban then shows only the matching runs in their respective lanes without affecting any other user's view of the same data.

 

Any new distinct value appears as its own lane at the end of the board the next time the page loads. You can drag the lane into the position you want, pick a color and an icon, and decide which fields the cards in that lane should display, without ever touching the AI Power database.

 

SleekView reads only the runs that fit in the current view, which is normally a few dozen even for very large sites. It piggybacks on the same indexes AI Power uses, so the board loads on a similar query budget to a default WordPress admin list and does not interfere with the cron worker.

 

Yes. Cost estimates are stored as a meta field on each run, and SleekView lets you choose any meta field as a card front element. You can show the estimated OpenAI cost next to the draft count so editors see the spend per run before dragging a card into the live lane.

 

SleekView never archives or deletes AI Power data on its own. Runs that move to live or rejected stay in their lanes until AI Power's own retention policy purges them. You can keep weeks of history visible by widening the date filter, or scope a board to the last seven days for a cleaner view.

 

Yes. SleekView ties drag permissions to WordPress capabilities, so a support role can view every lane, read every card detail, and even open the linked drafts in read-only mode. Drag actions that would change run_status to live or rejected are simply refused with an inline message.

 

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