Create Your First Record | 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.

Now that you’ve created your Objects, it’s time to add your first Records to them. In Kizen, a Record is a single entry of data inside an Object. It works similar to a row in a table, and stores all the information related to your Object grouping.

For example, if your Object is a collection of ticket data, then a Record would be all the data associated with one ticket or one purchase of tickets. The fields you define in your Object shape what data each Record contains.

In this topic, we continue following the Reyes family on their first visit to Flywheel Adventure Park. Your next step is to store Marcus’ Ticket purchase in the Tickets Object, then connect the ticket data back to the family's Contact Record. You will:

• Learn to create Ticket Object Data

• Learn how fields determine what data each Record can hold

• See how Record structure supports Workflows, Activities, Agentic Workflows, and reporting

• Apply those same steps to create data for the Concessions Object and Ride Waiver Object

These Records become the foundation for all operational processes in Flywheel Adventure Park and in your own business use cases.

Why This Matters

Well-structured Records impact nearly everything in Kizen, including:

• Accuracy: Clear fields prevent missing or duplicated data, for example, a dropdown for Stage Status ensures staff select Searching rather than typing it freehand.

• Agentic Workflows: Workflows depend on consistent field values to trigger correctly, such as sending a notification only when Stage Status changes to Located.

• Reporting: Dashboards and filters rely on clean, meaningful fields, a mislabeled stage can cause requests to disappear from operational reports.

• Scalability: Good Record structure grows with your operations without requiring rebuilds as processes expand.

• Activities: Logged or scheduled tasks pull data directly from Records, so a missing Contact field means staff can't follow up automatically.

When your Records are organized correctly, Workflows run without errors and your operational data tells a trustworthy story.

---

Before You Begin

To complete this task, you must:

• Have permissions to create and edit Records on the Objects you are modifying.

• Have completed:

  • Create Your First Contact Record

  • Create Your First Object

• You should also have three Objects already created:

  • Tickets for Marcus' purchase

  • Concessions for future food and snack purchases

  • Ride Waivers to capture permission forms the family must sign.

• You should also have Contact Records for all four family members

---

1

In the top navigation, select Data > Custom Objects

2

Select the Tickets Object

Note: The table on the Tickets page will be empty because you haven’t added any Records yet.

3

Create a new Record

Select NEW TICKET

Enter the following:

• Ticket Name: Marcus Reyes - Flywheel Tickets

• Owner: Yourself

• Ticket Value: $42.99

• Primary Contact: Marcus Reyes

• Visit Date: 06/15

• Number of Tickets: 4

• Admission Status: Unused

• Purchase Method: Online

4

Select SAVE

You will now see the purchase for the tickets are saved in the Object.

---

Apply What You’ve Learned

Next, you’ll create a Concession Record using the same steps you used for the Ticket Record you set up earlier.

1

Navigate back to the Objects page

Select BACK TO OBJECTS to return to the Objects page.

2

Select the Concessions Object

Selecting the Object will navigate you to the Concession Records page.

3

Enter your Record data

Select NEW CONCESSION and enter the following information.

• Concession Name: Popcorn

• Owner: Yourself

• Concession Value: $7.50

• Primary Contact Record: Sofia Reyes

• Quantity: 1

• Purchase Date: 6/15 at 2:30pm

4

Now, enter data for 3 other concessions

The data for the next three concessions can be found in the expanders below.

Fried Dough

• Concession Name: Fried Dough

• Owner: Yourself

• Concession Value: $8.50

• Primary Contact Record: Sofia Reyes

• Quantity: 1

• Purchase Date: 6/15 at 2:30pm

Cotton Candy

• Concession Name: Cotton Candy

• Owner: Yourself

• Concession Value: $6.00

• Primary Contact Record: Caleb Reyes

• Quantity: 1

• Purchase Date: 6/15 at 2:30pm

Soda

• Concession Name: Soda

• Owner: Yourself

• Concession Value: $4.50

• Primary Contact Record: Caleb Reyes

• Quantity: 1

• Purchase Date: 6/15 at 2:30pm

5

Finally, Navigate to the Ride Waiver Object and create a Record

Enter the following Ride Waiver Record:

• Ride Waiver Name: Sofia Reyes Ride Waiver

• Owner: Yourself

• Ride Name: Thunder Loop

• Guest Record: Sofia Reyes

• Waiver Date: 6/15 at 10:00 am

• Visit Date: 6/15

• Waiver Status: Signed

• Guardian Contact: Marcus Reyes

Your Records are now fully configured and connected.

---

How Records Power Agentic Workflows

Well-structured Records are the foundation of every Workflow and Agentic Workflow. Now that your Ticket, Concessions, and Ride Waiver Records exist, the system can begin connecting operational processes to the Reyes family’s visit.

These Records can trigger automated actions such as:

• Sending Marcus a ticket purchase confirmation email

• Scheduling a reminder email the day before the family’s visit

• Logging concession purchases during the park visit

• Recording Sofia’s completed ride waiver for staff verification

• Updating Timelines and related Records automatically as new activities occur

In the next lesson, you’ll build your first Workflow, using a Support Ticket Record as the trigger event.

Record Capabilities by Role

Admins

• Create, edit, reorder, and delete fields

• Modify Record layouts

• Configure relationships between Objects

• Manage permissions for Record editing

Technical Builders

• Use the Records API to create, update, or retrieve Records programmatically

• Build integrations using webhooks

• Map external data sources into Objects

• Create scalable schemas that support complex Agentic Workflows

---

Industry Applications

Records aren’t just for theme parks. In other industries, the same concepts apply.

Insurance

In insurance, Records represent the individual entries stored within each Object. These Records capture the specific details for applications, policies, claims, and other operational data used by insurers.

Common Records include:

• Applications

• Policies

• Claims

• Insured items

• Beneficiaries

Industry parallels to the Flywheel Adventure Park setup:

• Guests Record → Individual insured persons, dependents, or covered members

• Ticket Record → A policy or quote Record created for a customer

These Records allow insurers to:

• Track the details of individual applications, policies, and claims

• Capture information about insured assets or beneficiaries

• Maintain operational history for underwriting and servicing activities

Just as Flywheel Adventure Park stores ticket purchases as Records, insurance systems store applications, policies, and claims as Records within their respective Objects to support business operations.

Healthcare

Financial Services

---

What’s Next

Now that you’ve created your first Records, the next step is learning how to build a Workflow. In Create Your First Workflow, you’ll create a Workflow Object that tracks operational processes and moves records through defined stages.

For example, when Sofia realizes she left her backpack near one of the rides, park staff create a Lost Item Request that moves through stages such as Reported, Searching, and Resolved, ensuring the right staff members take action at each step.