In Jestor, approval flows accept dynamic thresholds combining two criteria at once: the amount of the request and the cost center involved, automatically routing it to the right approver in each case. The bottleneck of generic approvals Companies that grow and gain more cost centers often get stuck with overly
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
In Jestor, beyond the standard card style, the Kanban has three density levels: compact, mosaic, and compact mosaic — each one reduces the dead space between fields to fit more cards and more information on the same screen, without needing to open each record. The conflict between a nice-looking board
Jestor has more than 400 native automations, including direct integrations with Omie, Conta Azul, WhatsApp, Slack, Gmail, and more, with no intermediary required. Even so, for systems outside that native catalog, you can integrate via Zapier, Make, or open API and webhooks. The native catalog already covers almost everything In
In Jestor, a lookup field brings in a value that already exists in a connected table, without changing it, while a formula field processes a calculation — sum, multiplication, condition — from one or more fields, connected or not. The mistake of using the wrong field for the wrong data When structuring
In Jestor, there are three ways to start a new process: building from scratch (with AI or manually), cloning an existing table with its records, or installing one of the ready-made templates available in the Jestor store. The decision that stalls beginners Anyone structuring their operation for the first
In Jestor, each user can choose between the top menu, more compact, and the side menu, with more room for names, sections, and shortcuts organized by area — like building, automations, and user management. Generic navigation doesn't work for everyone Small and large teams have different navigation needs: whoever
In Jestor, you can generate PDFs two ways: by AI, where style and content are defined by a natural-language command at each generation, or by fixed automation, which always follows exactly the same layout rules. The tradeoff between standardization and flexibility Companies that need to send proposals, reports, or
In Jestor, a connected record can be displayed in two ways: as a card, with a cover image, background color, and summarized information, or as a superform, an editable mini-form with full blocks and fields. When the wrong view gets in the way of a decision Teams that just
In Jestor, there are two types of automation: button-triggered, which requires a manual action from the user, and event-triggered, which fires on its own when an event happens, like a card moving to a new phase or a field being changed. The risk of choosing the wrong automation
In Jestor Docs, every document can have three permission levels: private (only the author has access), shared for reading (everyone can read, but not edit), and shared for editing (everyone can read and edit the content). The risk of documentation with no access control Companies that use loose tools like
Yes. In Jestor, the chatbot agent can be configured with filters on its reference table, so it only sees and answers based on the records that pass that filter — for example, active deals only, ignoring the ones already closed-won or closed-lost. The risk of an agent with no