# How is Kizen Structured?

## Overview

Understanding how <code class="expression">space.vars.Kizen\_company\_name</code> 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** <code class="expression">space.vars.Kizen\_company\_name</code>

<table><thead><tr><th width="155.93359375">Concept</th><th>What It Is</th><th>How It Works</th><th>API</th></tr></thead><tbody><tr><td><a href="/pages/4qGNBmqyMwpbTrzVxa5A">Object</a></td><td>It's like a container or a table of data that stores grouped information (such as Guests, Tickets, Staff, or Equipment).</td><td>Provides the structure for your data. <code class="expression">space.vars.automations</code> and <code class="expression">space.vars.workflows</code> reference <code class="expression">space.vars.objects</code> to read, update, or create information.</td><td>Use the <a href="/pages/7LOKbYiimh48HDCKoLf4">Object endpoints</a> to create, describe, and manage <code class="expression">space.vars.objects</code>. <code class="expression">space.vars.object</code> IDs from these endpoints are required when working with <code class="expression">space.vars.entities</code>, filters, and <code class="expression">space.vars.automations</code>.</td></tr><tr><td><a href="/pages/0DyuKRuLvwyGKofOOxcN">Record</a></td><td>A single entry inside an <code class="expression">space.vars.object</code> (one guest, one ticket, one staff member, or one piece of equipment).</td><td>Holds the detailed information used by <code class="expression">space.vars.workflows</code>, charts, or <code class="expression">space.vars.dashboards</code>, and <code class="expression">space.vars.activities</code>. Most <code class="expression">space.vars.automation</code> logic ties back to specific <code class="expression">space.vars.entities</code>.</td><td>Use the <a href="/pages/Z8QhtksWkEpNcMiEf5xi">Records endpoints</a> to create, read, update, delete, and query <code class="expression">space.vars.entities</code> for a specific <code class="expression">space.vars.object</code>. Most endpoints accept <code class="expression">space.vars.object</code> identifiers plus filters, pagination parameters, and sorting options.</td></tr><tr><td><a href="/pages/doFOO2kMTGSp6AVc5may">Activities</a></td><td>Past Interactions or tasks logged to a <code class="expression">space.vars.entity</code> (calls, notes, updates, assignments).</td><td>Build history on a <code class="expression">space.vars.entity</code> and can trigger <code class="expression">space.vars.automations</code> or appear in <code class="expression">space.vars.dashboards</code> and <code class="expression">space.vars.timelines</code>.</td><td>Use the <a href="/pages/KPuP1nmDqHPgktEJkOCt">Activities endpoints</a> to create and fetch <code class="expression">space.vars.activities</code> tied to a <code class="expression">space.vars.entity</code>. Payloads typically include a <code class="expression">space.vars.entity</code> ID (or related <code class="expression">space.vars.object</code>/<code class="expression">space.vars.entity</code> reference) plus activity type, timestamp, and metadata.</td></tr><tr><td><a href="/pages/ym0ClLF9SGmtEOvHNsvA#scheduled-vs.-logged-activities">Scheduled Activities</a></td><td>Future <code class="expression">space.vars.activities</code> with a due date or time, such as appointments, reminders, or tasks.</td><td>Drive time-based <code class="expression">space.vars.workflows</code>, reminders, calendar <code class="expression">space.vars.automations</code>, and simple to-do lists that help users manage their daily work.</td><td>Use the <a href="/pages/KPuP1nmDqHPgktEJkOCt">Activities endpoints</a> with scheduling fields (start/due time, status). These can be combined with <code class="expression">space.vars.automations</code> endpoints or webhooks to react when a Scheduled <code class="expression">space.vars.activity</code> is created, updated, or completed.</td></tr><tr><td><a href="/pages/ym0ClLF9SGmtEOvHNsvA#timelines">Timelines</a></td><td>A chronological history of all interactions and <code class="expression">space.vars.activities</code> linked to a <code class="expression">space.vars.entity</code>. These can include Scheduled <code class="expression">space.vars.activities</code>.</td><td>Provide context for users and <code class="expression">space.vars.automations</code>, showing everything that has happened or will happen with that <code class="expression">space.vars.entity</code> in one place.</td><td>N/A</td></tr><tr><td><a href="/pages/ccTozjzRM3TDF6c3aICW">Agentic Workflows</a></td><td>Event-driven rules that move data and trigger actions, such as creating a follow-up task and sending a confirmation email when a <code class="expression">space.vars.contact</code> form is submitted.</td><td>Connect <code class="expression">space.vars.objects</code>, <code class="expression">space.vars.entities</code>, <code class="expression">space.vars.activities</code>, and external systems. Ensure processes run consistently and without manual effort.</td><td>Use <code class="expression">space.vars.Kizen_company_name</code>'s <strong>webhook framework</strong> to trigger <code class="expression">space.vars.automations</code> based on events in your external systems. You can configure these webhooks to send structured payloads to <code class="expression">space.vars.Kizen_company_name</code>, which then starts the appropriate <code class="expression">space.vars.workflow</code>.</td></tr><tr><td><code class="expression">space.vars.dashboards</code> &#x26; Charts</td><td>Charts that show trends, performance, and operational insights.</td><td>Pull data from <code class="expression">space.vars.objects</code>, <code class="expression">space.vars.entities</code>, <code class="expression">space.vars.activities</code>, and <code class="expression">space.vars.automations</code> to help teams monitor outcomes and make decisions.</td><td>N/A</td></tr></tbody></table>

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

{% columns %}
{% column %}

#### **Admins**

Admins configure <code class="expression">space.vars.objects</code>, fields, <code class="expression">space.vars.workflows</code>, views, and permissions.
{% endcolumn %}

{% column %}

#### **Technical Builders**

Technical Builders like developers, implementors, and solution architects extend functionality through APIs, integrations, and Marketplace tools.
{% endcolumn %}
{% endcolumns %}

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, <code class="expression">space.vars.objects</code>, <code class="expression">space.vars.workflows</code>, and <code class="expression">space.vars.dashboards</code> work together in a real scenario. This example will help you see [Kizen Basics in Action](/docs/kizen-basics/kizen-in-action.md) and connect these concepts before you begin building in your own Business workspace.

<details>

<summary>Related Topics</summary>

* [What is Kizen?](/docs/kizen-basics/what-is-kizen.md)
* [Kizen Basics in Action](/docs/kizen-basics/kizen-in-action.md)
* [Building with APIs](/docs/developers/building-with-apis.md)
* [Where to Find Help](/docs/readme/where-to-find-help.md)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/kizen-basics/how-is-kizen-structured.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.