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

Flywheel Adventure Park runs on recurring guest interactions: ticket purchases, waiver confirmations, gate check-ins, lost item reports, and concession sales. Staff need a consistent way to capture what happened, when, and who was involved.

Activities are how Kizen structures those interactions. Before your team can log or schedule anything, an administrator must create the Activity by defining its name, what it tracks, and how it connects to your workspace.

In this guide, you will create a Purchase Tickets Activity, which staff will use to track ticket purchases like the one made by the Reyes family.

Once created, the Activity is available across Kizen. Staff can schedule it ahead of a visit or log it on the spot, connecting it to Contact Records, Tickets, and other Records to power the Timeline, reporting, and downstream Agentic Workflows.

Why This Matters

Activities are the building blocks of how work gets tracked in Kizen. Without a defined Activity type, there's no consistent way for staff to Record that tickets were purchased, a waiver was confirmed, or a lost item was returned. Every team member would log these moments differently, and reporting would become unreliable.

By creating Activities thoughtfully, Flywheel Adventure Park ensures that:

• Staff have a shared vocabulary for the work they do every day

• Each interaction is captured in a structured, searchable way

• Timelines give a complete picture of every guest's journey

• Workflows and Agentic Workflows can trigger off real, consistent data

• Reports accurately reflect what's happening across the park

Creating your first Activity establishes the foundation that scheduling, logging, and Agentic Workflow all depend on.

---

Before You Begin

Before creating an Activity, make sure the following are in place:

• You have administrator permissions to create and configure Activities

• Your business workspace has been created and your business settings configured

• The Objects this Activity will associate with (such as Tickets and Contacts) have been created

• You've identified the team members who will schedule and log this Activity

• You understand the type of interaction this Activity should capture

Having these items ready ensures your Activity can be created and immediately connected to the rest of your workspace.

---

Creating an Activity

1

Navigate to Activities

From the top navigation, select Platform > Activities.

The Activities page appears, showing any Activities that already exist in your workspace.

2

Create a New Activity

On the Activities page, select NEW ACTIVITY in the upper-right corner.

An Add Activity modal appears.

3

Name Your Activity

In the Activity Name field, enter Purchase Tickets.

Select SAVE to create the Activity.

The Activity Settings page appears, where you'll configure the details.

4

Confirm Your Activity Settings

At the top of the Activity Settings page, you'll see six tabs: Activity Settings, Build, Team Sharing Settings, Advanced Rules, Scheduled/Logged, and Timeline.

You'll start on the Activity Settings tab. Here, confirm the Activity name reads Purchase Tickets. The API Name field auto-fills as purchase_tickets and is used when referencing this Activity through integrations or the API.

5

Add an Activity Description

In the Activity Description field, enter: This is when customers purchase tickets.

This description helps other admins and technical builders understand the purpose of the Activity when they encounter it later in Workflows, Agentic Workflows, or reports.

6

Configure Your Activity

1. Set the Default Submission Action

• Under Default Submission Action, leave the dropdown set to None.

2. Configure Notifications

• In the Notifications panel, you can notify team members by email or text each time this Activity is logged.

• For this first Activity, leave both Notify Team Members via Email and Notify Team Members via Text empty. You'll handle per-scheduled-Activity notifications (such as reminders to Marcus Reyes) when scheduling individual instances of this Activity.

3. Configure Calendar Integration

• In the Calendar Integration panel, leave Create Events for Scheduled Activities toggled off.

• When enabled, this setting sends a calendar invitation to the assigned team member whenever this Activity is scheduled. You can turn this on later if your team wants scheduled Activities to appear on their connected calendars.

4. Save Your Activity

• Your Activity is saved automatically as you configure it. You can now navigate back to the Activities page using BACK TO ACTIVITIES in the upper-left.

7

Save Your Activity

Your Activity is saved automatically as you configure it. You can now navigate back to the Activities page using BACK TO ACTIVITIES in the upper-left.

The Purchase Tickets Activity now appears in your Activities list and is available across the workspace for scheduling and logging.

---

Apply What You've Learned

Now that you've created one Activity, apply what you've learned. Create a second Activity using the same steps. This time, create a Ride Waiver Submissions Activity that Guest Services will use to track waiver completion for families visiting the park.

Use the information below to set it up.

Activity Settings

• Activity Name: Ride Waiver Submissions

• API Name: ride_waiver_submissions (auto-fills)

• Activity Description: Tracking Ride Waiver Submissions

• Default Submission Action: None

Notifications

• Notify Team Members via Email: Leave blank

• Notify Team Members via Text: Leave blank

Calendar Integration

• Create Events for Scheduled Activities: Off

When you've finished, both Purchase Tickets and Ride Waiver Submissions should appear in your Activities list, ready to be scheduled or logged.

---

How This Fits Into Agentic Workflows

Activities are the raw material thar Agentic Workflows act on. Once an Activity exists, it becomes available as a trigger, an action, and a data point across the platform.

In the Flywheel Adventure Park example, the Purchase Tickets Activity you just created can be used to:

• Trigger an Agentic Workflow that sends a purchase confirmation email to Marcus Reyes when tickets are logged for Sofia and Caleb

• Advance a guest-preparation Workflow once tickets are purchased, prompting the scheduling of Ride Waiver Confirmations

• Feed logged purchases into a sales dashboard showing daily ticket revenue and attendance projections

• Kick off a follow-up task for staff when a purchase includes add-ons that require additional setup

• Populate the Timeline on Marcus's Contact Record so any staff member can see his purchase history at a glance

Creating the Activity is step one. Scheduling and logging it, and then connecting it to Workflows and Agentic Workflows, is where operational value compounds.

---

Create Activity Capabilities by Role

Admins

• Create new Activity types and configure their settings

• Define Activity descriptions, API names, and default submission actions

• Configure logging notifications and calendar integration

• Manage team sharing settings and advanced rules for each Activity

• Archive or delete Activities that are no longer in use

Technical Builders

• Reference Activities by API name in integrations and custom code

• Trigger Agentic Workflows based on Activity scheduling or logging

• Build custom fields and forms on the Build tab to capture Activity-specific data

• Configure advanced rules to enforce required fields or conditional logic

• Connect logged Activity data to external systems and reporting tools

---

Tying It Back Into Your Industry

At Flywheel Adventure Park, creating a Purchase Tickets Activity establishes a consistent way to capture a recurring guest transaction. The same pattern, which involves defining a structured interaction type before tracking individual instances, applies across industries where repeatable transactions or touch points need to be captured reliably.

Insurance

Creating a Purchase Tickets Activity is similar to defining standard transactional Activities in insurance.

For example:

• A Policy Purchase Activity used every time a new policy is bound

• A Premium Payment Activity used whenever a payment is received

• A Coverage Add-On Activity used when a rider is added to an existing policy

Just as Flywheel Adventure Park standardizes how ticket purchases are tracked, insurance teams standardize how policy transactions are recorded.

Healthcare

Financial Services

---

What's Next?

Next, you'll learn how to Schedule an Activity, using the Activities you just created, to plan interactions ahead of time, assign them to team members, and connect them to Contacts, Tickets, and other Records across your workspace.