When should an internal process become a table app, and when should it become a Kanban?

In Jestor, tables are where the data lives — the process's relational database — while the Kanban is one of the possible views built on top of that table, focused on visually tracking stages.

The confusion between data structure and display

Anyone structuring a new process wonders whether to start by thinking about table columns or Kanban phases — and that confusion tends to produce poorly designed processes from the start.

This is more common in processes with clear progress stages, like sales or approvals, where the temptation to think about the Kanban first can leave the underlying data structure too shallow.

How to approach a new process

Always start with the table, defining the necessary fields and connections.
Add the Kanban afterward, if the process has visual progress stages.
Create the Kanban with one click from the existing table.
Apply color conditionals, filters, and card customization without altering the table.
Combine the table with multiple views: Kanban, list, dashboard, as the team needs.

Element	What it is	When to use it
Table	Relational data structure, with fields and connections	The base of any process, always needed
Kanban	A view built on top of the table, organized by phase	Processes with visual progress stages

Why choose Jestor?

Jestor lets you create a Kanban with one click from any existing table, with customizable colors, displayed fields, ordering, and conditionals — reinforcing Jestor as a process-automation tool for operations that still live in loose spreadsheets.

Frequently Asked Questions

Can a Kanban be created later, even if the table has existed for a while? Yes, the Kanban can be created at any time on top of an existing table, with one click.

Can I have more than one Kanban for the same table? Yes, different Kanbans can be created from the same dataset, each with its own focus.

Does every process necessarily need a Kanban? No, processes more focused on records and lookups can work well with just the table and list views.

Reference Video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and see how to take your company's management to a new level of efficiency and integration.

What signs show that a company has outgrown manual WhatsApp and needs native automation?

Companies still running things through a personal WhatsApp number or loose group chats eventually notice that the volume of conversations has outgrown their manual control — and that's the point where WhatsApp automation with AI agents in Jestor starts making a real difference in the operation. The symptoms of

How do you migrate a process that currently lives in a spreadsheet into a Jestor app without losing history?

In Jestor, you can upload an existing spreadsheet directly to the platform, and the system already suggests apps and structured processes built on top of the uploaded data, preserving the history that already existed. The fear of losing data during migration Companies that still manage entire processes in spreadsheets — sales,

Native Omie integration vs. contacting Jestor support: when is each one necessary?

In Jestor, the native integration with Omie is set up in a few minutes with an App Key and App Secret, covering approvals, entries, and orchestration across accounts. Contacting Jestor support, at request@jestor.email, is used for specific low-code setup requests, like connecting a template to Omie. When

AI agent that responds on its own vs. one with human verification: how do you set the level of autonomy?

In Jestor, AI agents can operate fully autonomously — responding, filling in fields, and even moving the card on their own — or in human-in-the-loop mode, where a person monitors and validates before the final action is confirmed. The hesitation to give full autonomy right away Companies automating WhatsApp