How is Kizen Structured?
Overview
Understanding how Kizen organizes and connects your data is the foundation for everything you build in the platform. For Admins and Technical builders, these building blocks make it easier to understand the platform, tailor your setup, and build workflows that make sense.
This topic walks through the key concepts, how they work together, and why they’re important to understand before you start hands-on setup.
Core Concepts In Kizen
It's like a container or a table of data that stores grouped information (such as Guests, Tickets, Staff, or Equipment).
Provides the structure for your data. Agentic Workflows and Workflows reference Objects to read, update, or create information.
Use the Object endpoints to create, describe, and manage Objects. Object IDs from these endpoints are required when working with Records, filters, and Agentic Workflows.
A single entry inside an Object (one guest, one ticket, one staff member, or one piece of equipment).
Holds the detailed information used by Workflows, charts, or Dashboards, and Activities. Most Agentic Workflow logic ties back to specific Records.
Use the Records endpoints to create, read, update, delete, and query Records for a specific Object. Most endpoints accept Object identifiers plus filters, pagination parameters, and sorting options.
Past Interactions or tasks logged to a Record (calls, notes, updates, assignments).
Build history on a Record and can trigger Agentic Workflows or appear in Dashboards and Timelines.
Use the Activities endpoints to create and fetch Activities tied to a Record. Payloads typically include a Record ID (or related Object/Record reference) plus activity type, timestamp, and metadata.
Future Activities with a due date or time, such as appointments, reminders, or tasks.
Drive time-based Workflows, reminders, calendar Agentic Workflows, and simple to-do lists that help users manage their daily work.
Use the Activities endpoints with scheduling fields (start/due time, status). These can be combined with Agentic Workflows endpoints or webhooks to react when a Scheduled Activity is created, updated, or completed.
A chronological history of all interactions and Activities linked to a Record. These can include Scheduled Activities.
Provide context for users and Agentic Workflows, showing everything that has happened or will happen with that Record in one place.
N/A
Event-driven rules that move data and trigger actions, such as creating a follow-up task and sending a confirmation email when a Contact form is submitted.
Connect Objects, Records, Activities, and external systems. Ensure processes run consistently and without manual effort.
Use Kizen's webhook framework to trigger Agentic Workflows based on events in your external systems. You can configure these webhooks to send structured payloads to Kizen, which then starts the appropriate Workflow.
Dashboards & Charts
Charts that show trends, performance, and operational insights.
Pull data from Objects, Records, Activities, and Agentic Workflows to help teams monitor outcomes and make decisions.
N/A
These components form a complete system for collecting data, managing work, and automating processes across your business.
Why Understanding This Structure Matters
Before you begin building, it’s important to understand how these concepts shape your environment:
Each component affects how data is stored, accessed, and used
Clear structure reduces confusion and prevents rework as your business scales
Different users interact with these components in different ways
A shared understanding of these building blocks ensures teams work from the same mental model.
What’s Next?
Move into a guided walkthrough that shows how data, Objects, Workflows, and Dashboards work together in a real scenario. This example will help you see Kizen Basics in Action and connect these concepts before you begin building in your own Business workspace.
Last updated
Was this helpful?