SleekView Kanban for Tally (embedded)
Tally embeds run on the Tally side, but a webhook can log every response to a WordPress table; SleekView reads that log, groups by state, and lets cards drag from New into Synced, Followed up, or Archived.
♾️ Lifetime License available
Tally embeds plus a webhook equals a queue worth visualising
Tally is a hosted form builder, and when its forms are embedded on a WordPress page the responses live on Tally's servers. Most installations route a webhook back to WordPress to keep a local trail: a row per response with response_id, form_id, submitted_at, state, and the JSON answers. Without a UI on top of that table, the team ends up triaging Tally responses by switching browser tabs and forgetting half of them.
SleekView Kanban reads the local log directly and groups by the state column. New holds fresh webhook hits, Synced covers responses that have been pushed onward (to a CRM, a Notion database, an email tool), Followed up flags the ones a human has actioned, and Archived clears the surface. Cards pull form name from a join, submitter email when the form collects one, the webhook delivery timestamp, and any answer the team wants pinned, including a priority field or a plan tier.
Dragging a card writes the new state back to the log table and fires a WordPress action so any add-on can react: a Notion sync can run on Synced, a Slack DM can fire on Followed up. The plugin or webhook handler still owns ingestion, the board just gives the queue a shape that matches the work.
Workflow
How SleekView Kanban reads Tally logs
Point at the response log table
tally_responses or similar via a webhook plugin. SleekView reads the schema, lists every column, and joins to WP posts holding the embed block for human-readable form names.
Group by state
state as the group-by. The board renders New, Synced, Followed up, and Archived columns with row counts in the header so backlog is obvious without scrolling.
Pin answers and context to cards
Enable drag-to-update
state to the log row and fires sleekview_kanban_status_change so downstream syncs can react without polling the log table.
Sample board
Sample Tally response board
Comparison
Default Tally response log vs SleekView Kanban
Default webhook log table
- Webhook table has no admin UI, so triage happens in Tally itself
- Switching to tally.so loses the WordPress role and capability model
- No board view of which responses synced and which still need action
- Followed-up state lives in Slack threads, not on the response
- Bulk archive needs SQL or a manual export
SleekView Kanban
-
Reads the local
tally_responseslog table directly -
Columns grouped by the
statecolumn with live counts - Cards parse JSON answers to surface priority, plan tier, or score
-
Drag fires
sleekview_kanban_status_changefor downstream pushes - Filters cover form ID, date range, and any answer-level field
Features
What SleekView Kanban gives you for Tally (embedded)
Local board for a hosted form
Tally owns the form and the response, the WordPress webhook owns the log. SleekView Kanban gives that log a board so the team triages Tally responses inside WordPress instead of switching to tally.so.
State changes via drag
Dragging a card writes the new state back to the log row and fires a WordPress action so a Notion sync, a Slack message, or a Linear ticket can react in the same beat.
Filters across forms
Saved views can scope to one Tally form, a date range, or an answer condition. A single board can cover all feedback forms with the form name shown on each card front.
Audience
Who triages Tally responses with SleekView Kanban
Product teams
Feature request forms feed Linear and Notion via webhook; the board confirms which responses synced and which ones still need a follow-up message.
Waitlist ops
Waitlist signups land in New, drag to Synced once added to Mailchimp, then Followed up after the welcome email goes out. Archived clears the surface after a month.
Support handoff
Responses tagged as a complaint move to Followed up the moment a ticket opens, with the original response visible on the card for context.
The bigger picture
Why Tally responses deserve a WordPress board
Tally is a great hosted form builder, and embedding it on a WordPress page is a one-block job. The downside is that the team's workflow lives split across two tools: the response sits on Tally, the user account and role model live on WordPress, and any downstream system (Notion, Linear, Mailchimp) gets the response via a webhook the team has wired up. Without a board view on the WordPress side, the webhook log is just rows in a database.
SleekView Kanban reshapes that log into a queue. State becomes the axis, the columns reflect how responses actually flow, and a drag updates the state with a hook that lets every downstream tool stay in sync. Tally keeps owning form design and submission, the webhook handler keeps owning ingestion, and the team finally has a triage surface where the rest of their work already happens.
Questions
Common questions about SleekView Kanban for Tally (embedded)
Yes. Tally stores responses on its own servers. To use SleekView Kanban you need a webhook handler (a small custom endpoint or a logging plugin) that writes one row per response to a WordPress table, with at minimum a status or state column to group by.
Whatever your webhook handler writes the state to, commonly state or sync_status. SleekView lists every text or enum column on the log table and lets you pick. The values become the columns and the row counts become the header.
Yes. SleekView parses the JSON answer blob and lets you pin specific fields to the card front, like priority or plan tier. Filters can also be expressed against those answers, so a board can scope to high-priority responses without exporting.
SleekView updates the state column on the log row and fires a sleekview_kanban_status_change action with the row ID and new state. A small WordPress snippet or any add-on can listen and trigger a Notion sync, a Slack ping, or a follow-up email.
Yes. The form_id column is filterable and the card front can show the form name. Saved views support one form, several forms, or all forms, with role-based access controlled by WordPress capabilities.
Yes. SleekView paginates per column and queries indexed columns on the log table. JSON answer parsing runs only for the rows currently rendered, so a log with hundreds of thousands of rows still renders the visible columns quickly.
No. SleekView Kanban is a read and update surface for the local log. If you need to call Tally's API on a state change (to close a response, for example), wire that into your snippet listening for sleekview_kanban_status_change.
No. Tally's design tools, response views, and analytics stay where they are. The kanban view adds a triage surface inside WordPress for the local response log so embedded forms get a workflow without copying data into another tool.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout