Create Your First Object | Kizen Basics

Overview

Caution: This setup reflects Kizen's default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.

In Kizen, an Object is like a table or a data container that you create to store and organize the data that matters to your business. Objects hold the Records you’ll reference in Agentic Workflows, Dashboards, and Workflows. Contacts store the people you need to communicate with, Objects store everything else — tickets, ride waivers, concessions, assets, tasks, memberships, and more.

In this walkthrough, you’ll create three Objects for Flywheel Adventure Park:

• Tickets Object: to store ticket purchases and visitor passes, such as Marcus’s family admission

• Concessions Object: to capture food and merchandise purchases made during park visits

• Ride Waiver Object: to store and track ride waivers signed by guests

These Objects will become the foundation for your next steps, including creating Records and building Workflows that automate communication, follow-up tasks, and daily park operations.

Why This Matters

Objects define where your data lives and how it’s structured. Clear Object design prevents errors later, such as:

• Workflows not triggering correctly

• Agentic Workflows missing required fields

• Reports failing to show accurate information

• Disorganized or duplicated data across your business

A well-planned Object gives your team a consistent, scalable data foundation. Now, lets start by creating your Tickets Object.

Before You Begin

Before creating an Object, you must have the following:

• Admin permissions with the ability to create and edit Records

• A Business workspace created

---

1

Navigate to Objects

1. In the top navigation, select Data.

2. Choose Custom Objects.

The Objects page opens with a default Companies Object already created. You won't need it for this walkthrough — feel free to delete it by selecting the ellipsis in the Actions column. If your real-world use case involves companies, keep it.

2

Select NEW OBJECT

The Reyes family includes four visitors. Earlier, you created Contact Records to store information about each member of the family.

Now, you will create a Tickets Object to store ticket purchases made for park visits. This Object will define the structure used to capture purchases, such as who bought the tickets, how many were purchased, and the date of the visit.

Note: In later steps, you will create Ticket Records within this Object to track purchases like the one Marcus made for his family.

First, select the NEW OBJECT button. You will be taken to the General Settings page for your Object.

3

Fill out the General Settings page

For this example, you will enter the following:

• Object Name: Tickets

Note: This is the name of the Object and represents the type of data you’re tracking. An Object is like a table or container, so this name describes the collection of Records it will hold.

• Record Name: Ticket

Note: This is the name you want to call an individual Record in your Object. Remember, this is a specific Record inside of your collection of data. Currently, this is called Entity Name in the UI.

• Contains Workflow: Disable

Note: This feature is used for creating opportunity or deal pipelines and ticket workflows. We won’t use it in this example, but you’ll learn how it works in the Create Your First Workflow topic.

• Enable Quick Filters: Disable

• Object Description: Stores Records of ticket purchases made for park visits. This Object tracks details such as the purchaser, number of tickets, visit date, and other information related to admission.

• Enable Activities: Enabled

• Track Track Entity $ Value: Enabled

4

Select SAVE & CONTINUE

This will automatically save your Object and take you to the Related Objects step below.

Note: The Contacts relationship appears by default but isn't saved until you select SAVE & CONTINUE.

Next, we need to create a relationship between the Tickets Marcus purchased in the Tickets Object and his Contact information in the Contacts Object so we can keep track of who purchased what tickets. To do this, under Related Objects.

Then enter the following:

• Related Object: Contacts

• Relationship Type: Many-to-One

• Relationship Name: Purchaser Contact

• Reverse Relationship Name: Related Ticket Records

Select SAVE & CONTINUE.

5

Modify Step 3 Customize Fields

Here is where you can Customize your Object Fields. The Custom Field acts like a column in your table of data inside your Object. As you can see, when you created your Object, Kizen automatically created table columns for you.

Note: Kizen automatically creates the Ticket Name field as the unique identifier for this Object.

Now, we will create new column data. Select +ADD NEW FIELD and create the following so we can properly capture your Ticket data. Add the following fields:

Note: That you do not need to change the Category or Description Visibility settings for this example.

Field Name	Description	Field Type	Field Purpose
Visit Date	The date the tickets are valid for entry to the park.	Date	Tracks when the guest plans to visit the park.
Number of Tickets	The total number of tickets purchased in the transaction.	Number (Whole)	Records how many admissions were purchased for the visit.
Admission Status	Indicates whether the ticket has been used for entry.	Dropdown. (Unused,Used)	Tracks whether the ticket has been used or is still unused.
Purchase Method	Tracks how the tickets were purchased.	Dropdown (Online, In Person, Telephone	Identifies the source of the purchase, such as Online or In Person.

All new Custom Fields should be visible in your Ticket info category including the relationship field you created in step 2.

Select NEXT STEP to continue.

Note: You can use the ADD NEW CATEGORY feature to organize your Custom Fields by category.

6

Select Default Columns tab from Step 4 Customize Layout

Here is where you can take the Custom Fields you just created and then organize them on your Ticket Overview table.

Lets add the following fields we just created:

• Purchaser Contact

• Visit Date

• Number of Tickets

• Admission Status

• Purchase Method

Lets remove the columns we don't need that came standard with the Tickets Object.

• Owner

• Display Name

• Last Modified

7

Select SAVE & CLOSE

Your Tickets Object is now ready to store Records and support Workflows later in the walkthrough.

---

Apply What You've Learned

With the Tickets Object now complete, it’s time to apply what you have learned to create Concessions and Ride Waiver Objects using the same steps. These Objects will track purchases made in the park and adherence to safety policies.

Use the information below to set it up.

• Object Name: Concessions

• Record (Entity) Name: Concession

• Enable Workflows: Disable

• Enable Quick Filters: Disable

• Object Description: Stores records of concession purchases, including the product purchased, purchase date, visit date, and the Contact who made the purchase.

• Enable Activities: Enabled

• Track Track Entity $ Value: Enabled

Create Your Fields For The Concessions Object

Note: For this example do not modify the Category or Description Visibility fields.

Field Name	Description	Field Type	Field Purpose
Concession Name (Unique Identifier)	A unique name for the concession purchased	Text (Unique Identifier)	Identifies the concession purchase Record within the Concessions Object.
Concession Value	The total cost of the concession purchase.	Currency	Tracks the revenue generated from the purchase.
Primary Contact	The Contact Record of the person who made the purchase.	Relationship (Contacts)	Links the concession purchase to the person responsible for the order.
Purchase Date	The date the concession item was purchased.	Date/Time	Tracks when the purchase occurred.
Quantity	The number of items purchased.	Number (Whole)	Captures how many units of the item were purchased.

Customize Your Default Columns

Now Navigate to Customize Layout > Default Columns and move your columns as follows

Available Columns

Owner

Date Created

Display Name

Last Modified

Active Table Columns

Concession Name

Concession Value

Primary Contact Record

Purchase Date

Quantity

Select SAVE & CONTINUE, then FINALIZE YOUR OBJECT (you do not need to set permissions at this time). Now your Concessions Object is now ready for Record creation and Agentic Workflow triggers (such as sending confirmation messages or creating follow-up tasks)!

Now create one more new Object for ride waivers and use the information below to set it up.

• Object Name: Ride Waivers

• Record (Entity) Name: Ride Waiver

• Enable Workflows: Disable

• Enable Quick Filters: Disable

• Object Description: Stores Records of ride waivers signed for park attractions, including the ride name, waiver date, visit date, and the Contact associated with the waiver.

• Enable Activities: Enabled

• Track Track Entity $ Value: Disabled

Field Name	Description	Field Type	Field Purpose
Ride Waiver Name (Unique Identifier)	A unique name for the waiver Record.	Text (Unique Identifier)	Identifies the waiver Record within the Ride Waiver Object.
Guest Record	The Contact Record of the guest who requires the waiver.	Relationship: Contacts	Links the waiver to the individual guest participating in the ride.
Ride Name	The name of the ride requiring the waiver.	Text	Identifies which attraction the waiver applies to.
Waiver Date	The date the waiver was signed or approved.	Date/Time	Tracks when the waiver was completed.
Visit Date	The date of the park visit is associated with the waiver.	Date	Links the waiver to a specific park visit.
Waiver Status	Indicates whether the waiver has been signed and approved.	Dropdown (Pending, Signed, Verified)	Tracks whether the guest has completed the required waiver.
Guardian Contact	The Contact Record of the parent or guardian who signed the waiver.	Relationship: Contacts	Captures who approved the waiver if the guest is a minor.

Ensure that you have customized your fields so only the ones shown above are visible!

---

How This Fits Into Agentic Workflows

Now that Flywheel Adventure Park has Tickets, Concessions, and Ride Waiver Objects, Kizen can begin connecting real processes to the Reyes family’s visit. Each Object captures a different part of the guest experience, from ticket purchases, to food purchases, to required ride permissions.

When Marcus’s Ticket Record is created, it becomes the event that starts everything:

• A welcome email is sent

• Staff are assigned tasks

• Ride Waivers are sent out and wristbands are prepared

• A follow-up survey is scheduled

These Workflows and Agentic Workflows work best when the underlying Objects and Records are structured correctly, which is why defining these Objects is an essential step before Creating Your First Workflow.

---

Object Capabilities By Role

Admins

• Create and manage Objects

• Add or modify fields

• Control permissions and relationships between Object

• Prepare data structures for Workflows, Dashboards, and Agentic Workflows

Technical Builders

• Integrate external systems using webhooks or ETL pipelines to populate Object

• Leverage Record-level APIs to sync tickets and guest data from other platforms

• Build scalable data models with future Agentic Workflows in mind

---

Tying It Back Into Your Industry

The three Objects you created for the Reyes family are specific to Flywheel Adventure Park, but the same structure applies across many industries. Objects are how you model your business — they represent the data you track, the processes you automate, and the relationships your Workflows depend on.

Below are examples of how the concepts in this walkthrough translate into real-world use cases in Healthcare, Insurance, and Financial Services.

Insurance

In insurance, Objects represent the structured data and processes that define underwriting, quoting, policy management, and claims.

Common Objects include:

• Applications

• Policies

• Vehicles, Properties, or Insured Assets

• Claims

• Beneficiaries

• Supporting Documents

Industry parallels to the Flywheel Adventure Park setup:

• Tickets Object → Policy or Quote Records linked to a Contact (applicant)

• Concessions Object → Transactions related to a policy, such as premium payments, service fees, or endorsements

• Ride Waivers Object → Signed disclosures, acknowledgments, or compliance documents required for coverage

Objects allow insurers to:

• Trigger Workflows when an application is submitted

• Route tasks to underwriting or claims teams

• Generate policy documents

• Automate renewal reminders

• Track multi-step processes with full audit history

Just like Flywheel Adventure Park uses Tickets to start visit Workflows, an Application or Claim Object can trigger Agentic Workflows that route work through the appropriate teams.

Healthcare

Financial Services

---

What’s Next?

Now that your Tickets, Concession, and Ride Waiver Objects are created, you’re ready to add real data to your workspace. In the next topic, Create Your First Record, you’ll enter the following Records:

• Marcus’s purchased ticket into the Tickets Object

• The Reyes family snack purchase in the Concessions Object

• Sofia’s ride waiver in the Ride Waiver Object

These Records will prepare your workspace for building your first Workflow, where the system can trigger actions such as sending confirmations, creating tasks, or tracking guest activities.