# Create Your First Activity | Kizen Basics

## Overview

{% hint style="warning" %}
**Caution**: This setup reflects <code class="expression">space.vars.Kizen\_company\_name</code>'s default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

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.

<code class="expression">space.vars.activities</code> are how <code class="expression">space.vars.Kizen\_company\_name</code> structures those interactions. Before your team can log or schedule anything, an administrator must create the <code class="expression">space.vars.activity</code> by defining its name, what it tracks, and how it connects to your workspace.

In this guide, you will create a **Purchase Tickets** <code class="expression">space.vars.activity</code>, which staff will use to track ticket purchases like the one made by the Reyes family.

Once created, the <code class="expression">space.vars.activity</code> is available across <code class="expression">space.vars.Kizen\_company\_name</code>. Staff can schedule it ahead of a visit or log it on the spot, connecting it to <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>, Tickets, and other <code class="expression">space.vars.entities</code> to power the <code class="expression">space.vars.timeline</code>, reporting, and downstream <code class="expression">space.vars.automations</code>.

### Why This Matters

<code class="expression">space.vars.activities</code> are the building blocks of how work gets tracked in <code class="expression">space.vars.Kizen\_company\_name</code>. Without a defined <code class="expression">space.vars.activity</code> type, there's no consistent way for staff to <code class="expression">space.vars.entity</code> 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 <code class="expression">space.vars.activities</code> thoughtfully, <code class="expression">space.vars.Theme\_park\_name</code> 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
* <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> can trigger off real, consistent data
* Reports accurately reflect what's happening across the park

Creating your first <code class="expression">space.vars.activity</code> establishes the foundation that scheduling, logging, and <code class="expression">space.vars.automation</code> all depend on.

***

## Before You Begin

Before creating an <code class="expression">space.vars.activity</code>, make sure the following are in place:

* You have administrator permissions to create and configure <code class="expression">space.vars.activities</code>
* Your business workspace has been created and your business settings configured
* The <code class="expression">space.vars.objects</code> this <code class="expression">space.vars.activity</code> will associate with (such as Tickets and Contacts) have been created
* You've identified the team members who will schedule and log this <code class="expression">space.vars.activity</code>
* You understand the type of interaction this <code class="expression">space.vars.activity</code> should capture

Having these items ready ensures your <code class="expression">space.vars.activity</code> can be created and immediately connected to the rest of your workspace.

***

## Creating an Activity

{% stepper %}
{% step %}

#### Navigate to **Activities**

From the top navigation, select **Platform > Activities**.

The <code class="expression">space.vars.activities</code> page appears, showing any <code class="expression">space.vars.activities</code> that already exist in your workspace.
{% endstep %}

{% step %}

#### Create a **New Activity**

On the <code class="expression">space.vars.activities</code> page, select **NEW ACTIVITY** in the upper-right corner.

<div data-with-frame="true"><figure><img src="/files/shogQalMu750NsWlyHws" alt=""><figcaption></figcaption></figure></div>

An **Add Activity** modal appears.
{% endstep %}

{% step %}

#### Name Your Activity

In the **Activity Name** field, enter **Purchase Tickets**.

<div data-with-frame="true"><figure><img src="/files/NZguo6juA7QKvGkhYvzs" alt="" width="375"><figcaption></figcaption></figure></div>

Select **SAVE** to create the <code class="expression">space.vars.activity</code>.

The <code class="expression">space.vars.activity</code> Settings page appears, where you'll configure the details.
{% endstep %}

{% step %}

#### Confirm Your Activity Settings

At the top of the <code class="expression">space.vars.activity</code> 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 <code class="expression">space.vars.activity</code> name reads **Purchase Tickets**. The **API Name** field auto-fills as `purchase_tickets` and is used when referencing this <code class="expression">space.vars.activity</code> through integrations or the API.

<div data-with-frame="true"><figure><img src="/files/ePfdmbjMyMmuJfyeoBb4" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### 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 <code class="expression">space.vars.activity</code> when they encounter it later in <code class="expression">space.vars.workflows</code>, <code class="expression">space.vars.automations</code>, or reports.
{% endstep %}

{% step %}

#### Configure Your Activity&#x20;

**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 <code class="expression">space.vars.activity</code> is logged.
* For this first <code class="expression">space.vars.activity</code>, leave both **Notify Team Members via Email** and **Notify Team Members via Text** empty. You'll handle per-scheduled-<code class="expression">space.vars.activity</code> notifications (such as reminders to Marcus Reyes) when scheduling individual instances of this <code class="expression">space.vars.activity</code>.

**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 <code class="expression">space.vars.activity</code> is scheduled. You can turn this on later if your team wants scheduled <code class="expression">space.vars.activities</code> to appear on their connected calendars.

**4. Save Your Activity**

* Your <code class="expression">space.vars.activity</code> is saved automatically as you configure it. You can now navigate back to the <code class="expression">space.vars.activities</code> page using **BACK TO ACTIVITIES** in the upper-left.
  {% endstep %}

{% step %}

### Save Your Activity

Your <code class="expression">space.vars.activity</code> is saved automatically as you configure it. You can now navigate back to the <code class="expression">space.vars.activities</code> page using **BACK TO ACTIVITIES** in the upper-left.
{% endstep %}
{% endstepper %}

The Purchase Tickets <code class="expression">space.vars.activity</code> now appears in your <code class="expression">space.vars.activities</code> list and is available across the workspace for scheduling and logging.

***

## Apply What You've Learned

Now that you've created one <code class="expression">space.vars.activity</code>, apply what you've learned. Create a second <code class="expression">space.vars.activity</code> using the same steps. This time, create a **Ride Waiver Submissions** <code class="expression">space.vars.activity</code> 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 <code class="expression">space.vars.activities</code>: Off

When you've finished, both **Purchase Tickets** and **Ride Waiver Submissions** should appear in your <code class="expression">space.vars.activities</code> list, ready to be scheduled or logged.

***

## How This Fits Into Agentic Workflows

<code class="expression">space.vars.activities</code> are the raw material thar <code class="expression">space.vars.automations</code> act on. Once an <code class="expression">space.vars.activity</code> exists, it becomes available as a trigger, an action, and a data point across the platform.

In the <code class="expression">space.vars.Theme\_park\_name</code> example, the Purchase Tickets <code class="expression">space.vars.activity</code> you just created can be used to:

* Trigger an <code class="expression">space.vars.automation</code> that sends a purchase confirmation email to Marcus Reyes when tickets are logged for Sofia and Caleb
* Advance a guest-preparation <code class="expression">space.vars.workflow</code> 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 <code class="expression">space.vars.timeline</code> on Marcus's <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> so any staff member can see his purchase history at a glance

Creating the <code class="expression">space.vars.activity</code> is step one. Scheduling and logging it, and then connecting it to <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code>, is where operational value compounds.

***

## Create Activity Capabilities by Role

{% columns %}
{% column %}

### Admins

* Create new <code class="expression">space.vars.activity</code> types and configure their settings
* Define <code class="expression">space.vars.activity</code> descriptions, API names, and default submission actions
* Configure logging notifications and calendar integration
* Manage team sharing settings and advanced rules for each <code class="expression">space.vars.activity</code>
* Archive or delete <code class="expression">space.vars.activities</code> that are no longer in use
  {% endcolumn %}

{% column %}

### Technical Builders

* Reference <code class="expression">space.vars.activities</code> by API name in integrations and custom code
* Trigger <code class="expression">space.vars.automations</code> based on <code class="expression">space.vars.activity</code> scheduling or logging
* Build custom fields and forms on the Build tab to capture <code class="expression">space.vars.activity</code>-specific data
* Configure advanced rules to enforce required fields or conditional logic
* Connect logged <code class="expression">space.vars.activity</code> data to external systems and reporting tools
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back Into Your Industry

At <code class="expression">space.vars.Theme\_park\_name</code>, creating a Purchase Tickets <code class="expression">space.vars.activity</code> 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.

{% tabs %}
{% tab title="Insurance" %}
Creating a Purchase Tickets <code class="expression">space.vars.activity</code> is similar to defining standard transactional Activities in insurance.

For example:

* A Policy Purchase <code class="expression">space.vars.activity</code> used every time a new policy is bound
* A Premium Payment <code class="expression">space.vars.activity</code> used whenever a payment is received
* A Coverage Add-On <code class="expression">space.vars.activity</code> used when a rider is added to an existing policy

Just as <code class="expression">space.vars.Theme\_park\_name</code> standardizes how ticket purchases are tracked, insurance teams standardize how policy transactions are recorded.
{% endtab %}

{% tab title="Healthcare" %}
In healthcare, a defined <code class="expression">space.vars.activity</code> corresponds to a standard patient-encounter type.

For example:

* An Appointment Scheduled <code class="expression">space.vars.activity</code> used when a visit is booked
* A Co-Pay Collection <code class="expression">space.vars.activity</code> used at check-in
* A Prescription Fulfilled <code class="expression">space.vars.activity</code> used when medication is dispensed

These Activities ensure every patient transaction is captured the same way, regardless of which staff member handles it.
{% endtab %}

{% tab title="Financial Services" %}
In financial services, <code class="expression">space.vars.activities</code> map to recurring client transactions and service events.

For example:

* A New Account Opened <code class="expression">space.vars.activity</code> used during onboarding
* A Deposit Received <code class="expression">space.vars.activity</code> used for incoming funds
* A Trade Executed <code class="expression">space.vars.activity</code> used when an order is filled

Standardizing these <code class="expression">space.vars.activities</code> makes client service consistent and auditable, no matter who performs the work.
{% endtab %}
{% endtabs %}

***

## What's Next?

Next, you'll learn how to [Schedule an Activity](/docs/kizen-basics/kizen-in-action/scheduling-your-activity-and-timelines-or-kizen-in-action.md), using the <code class="expression">space.vars.activities</code> you just created, to plan interactions ahead of time, assign them to team members, and connect them to <code class="expression">space.vars.contacts</code>, Tickets, and other <code class="expression">space.vars.entities</code> across your workspace.


---

# 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/kizen-in-action/create-your-first-activity-or-kizen-basics.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.