# Activities Core Concepts

{% hint style="success" %}
**Audience:** Technical Builders, Implementors, and Developers

**Purpose:** Explains how <code class="expression">space.vars.activities</code> function within <code class="expression">space.vars.Kizen\_company\_name</code>’s data model, so builders can design reliable <code class="expression">space.vars.automations</code>, integrations, and API workflows.
{% endhint %}

## Overview

An <code class="expression">space.vars.activity</code> represents a human-initiated interaction or a planned touchpoint. Each <code class="expression">space.vars.activity</code> is an instance of its respective <code class="expression">space.vars.activity</code> <code class="expression">space.vars.object</code>, which defines the schema, required fields, and allowed associations for a given <code class="expression">space.vars.activity</code> type.

Each <code class="expression">space.vars.activity</code> contains:

* **System Fields:** Fields that define the <code class="expression">space.vars.activity</code>’s identity, scheduling, and associations, such as:
  * <code class="expression">space.vars.activity</code> name (for example, call, meeting, inspection)
  * One or more associated <code class="expression">space.vars.entities</code> (such as a <code class="expression">space.vars.contact</code> or <code class="expression">space.vars.object</code>), all <code class="expression">space.vars.entities</code> of an <code class="expression">space.vars.object</code> type, or no associated <code class="expression">space.vars.entities</code>
  * Timestamps (`due_datetime`, `logged_at`)
* **Activity Fields:** Fields that are defined and stored directly on the <code class="expression">space.vars.activity</code> <code class="expression">space.vars.entity</code>, including:
  * Notes and descriptions
  * Participants or mentions
  * Categories or tags applied to the <code class="expression">space.vars.activity</code>
* **Custom Fields:** Fields that are displayed and editable from the <code class="expression">space.vars.activity</code>, but whose values are stored on a related <code class="expression">space.vars.object</code>. These are any <code class="expression">space.vars.fields</code> configured for the <code class="expression">space.vars.activity</code> type.

#### System Behavior

Once an <code class="expression">space.vars.activity</code> has been created (either logged or scheduled), an <code class="expression">space.vars.activity</code>:

* Appears on each associated <code class="expression">space.vars.entities</code> <code class="expression">space.vars.timeline</code>
* Can trigger <code class="expression">space.vars.automations</code>
* Updates reporting datasets
* Is accessible via API, <code class="expression">space.vars.automations</code>, or UI
* Sends webhook events (only when logged)

***

## Why Activities Matter

<code class="expression">space.vars.activities</code> help teams understand the full context of each associated <code class="expression">space.vars.entity</code>, including:

* Shared interaction history: <code class="expression">space.vars.activities</code> provide a chronological <code class="expression">space.vars.entity</code> of human interactions associated with a <code class="expression">space.vars.entity</code>.
* Clear task management: Scheduled and Logged <code class="expression">space.vars.activities</code> distinguish to-do tasks from completed tasks.
* Flexible activity trackin&#x67;**:** <code class="expression">space.vars.activities</code> can represent work beyond communication, such as internal tasks, follow-ups, reviews, or reminders, and may be associated with <code class="expression">space.vars.contacts</code>, <code class="expression">space.vars.entities</code>, or stand alone.
* Standardized engagement data: <code class="expression">space.vars.activity</code> Objects define consistent schemas for capturing calls, meetings, and other touch points.
* Reliable handoffs: <code class="expression">space.vars.activities</code> preserve context, outcomes, and ownership so work can continue without reconstruction.
* <code class="expression">space.vars.automation</code> and integration hooks: <code class="expression">space.vars.activity</code> lifecycle events can trigger <code class="expression">space.vars.automations</code> or external <code class="expression">space.vars.workflows</code> via APIs and webhooks.
* Reporting and analytics inputs: <code class="expression">space.vars.activities</code> supply structured engagement data for <code class="expression">space.vars.dashboards</code>, reports, and operational metrics.

***

## Scheduled vs. Logged Activities

A Scheduled <code class="expression">space.vars.activity</code> represents a human interaction that has not yet occurred or a to-do task, while a Logged <code class="expression">space.vars.activity</code> represents a completed interaction or task. A Scheduled <code class="expression">space.vars.activity</code> *transitions into* a Logged <code class="expression">space.vars.activity</code> once the task has been completed and the outcome is recorded.&#x20;

This transition affects how the <code class="expression">space.vars.activity</code> behaves in the system:&#x20;

* Scheduled <code class="expression">space.vars.activities</code> are mutable and used for planning
* Logged <code class="expression">space.vars.activities</code> are immutable and serve as a historical <code class="expression">space.vars.entity</code>.&#x20;

Lifecycle transitions can trigger <code class="expression">space.vars.automations</code>, webhooks, and reporting updates. The differences between the two are outlined below.

| Attribute                  | Scheduled Activity                            | Logged Activity                                |
| -------------------------- | --------------------------------------------- | ---------------------------------------------- |
| **What it represents**     | An interaction or task planned for the future | An interaction or task that has occurred       |
| **Lifecycle state**        | Pre-execution                                 | Post-execution                                 |
| **When it's created**      | Before the interaction or task                | After the interaction or task                  |
| **Primary timestamps**     | `due_datetime`                                | `logged_at` / `completed_at`                   |
| **Mutability**             | Can be updated, rescheduled, or canceled      | Can only be appended to                        |
| **Timeline behavior**      | Appears as upcoming                           | Appears as completed                           |
| **Agentic Workflow usage** | Drives reminders and time-based triggers      | Drives completion-based triggers and reporting |
| **State transition**       | Converts to a Logged Activity when completed  | Does not transition to another state           |
| **Trigger Webhooks**       | Cannot trigger webhooks                       | Can trigger webhooks                           |

***

## How Activities are Used

<code class="expression">space.vars.activities</code> appear across multiple areas of the <code class="expression">space.vars.Kizen\_company\_name</code> platform, allowing the same interaction data to support planning, execution, visibility, and automation.

### **Calendars**

<code class="expression">space.vars.activities</code> with a scheduled date and time appear on calendars. This helps teams see upcoming tasks, plan capacity, and manage time-based commitments without duplicating data in a separate scheduling system.

### **Agentic Workflows**

<code class="expression">space.vars.activities</code> can trigger <code class="expression">space.vars.automations</code> or be created by them. This allows workflows to respond to real interactions, such as sending follow-ups after a call is logged or scheduling reminders when an <code class="expression">space.vars.activity</code> is created. <code class="expression">space.vars.activity</code> lifecycle events, such as creation, updates, and completion, can trigger <code class="expression">space.vars.automations</code> within <code class="expression">space.vars.Kizen\_company\_name</code> or be consumed via APIs and webhooks by external systems.

### **Dashboards**

<code class="expression">space.vars.activity</code> data feeds dashboards and reports. Teams can measure volume, timing, completion rates, and outcomes of interactions to understand performance and operational trends.

### **Timelines**

<code class="expression">space.vars.activities</code> appear in Timelines alongside other relevant events. This gives teams a chronological view of what happened and what’s planned, providing full context for each <code class="expression">space.vars.contact</code> or <code class="expression">space.vars.entity</code>.

These surfaces reflect <code class="expression">space.vars.activity</code> data but do not own it. The <code class="expression">space.vars.activity</code> <code class="expression">space.vars.entity</code> remains the source of truth.

***

## Key Use Cases

From a builder or system perspective, <code class="expression">space.vars.activities</code> support workflows such as:

* Workflow management (sales calls, demos, negotiations)
* Service delivery tracking (on-site visits, inspections, appointments)
* Support processes (case updates, customer follow-ups)
* Compliance workflows (document reviews, required touch points)
* Operational logging (visit logs, check-ins, approvals)
* Engagement-based <code class="expression">space.vars.automations</code> (triggering workflows from <code class="expression">space.vars.activity</code> events)

Because <code class="expression">space.vars.activities</code> are exposed through APIs and <code class="expression">space.vars.automations</code>, they function as a shared engagement object across the entire platform.

### Industry Examples

<code class="expression">space.vars.activities</code> are flexible and can support any workflow. These short examples highlight how three different industries use <code class="expression">space.vars.activities</code> to capture human interactions.

{% tabs %}
{% tab title="Insurance" %}

#### Insurance Teams Managing Policyholder Interactions

Insurance workflows use <code class="expression">space.vars.activities</code> to capture structured <code class="expression">space.vars.entities</code> of every interaction across the policy lifecycle, supporting underwriting, compliance, renewals, and automation.

**Examples include:**

* Logging an Initial Coverage Consultation documenting coverage needs, risk factors, and existing policies
* Recording a Quote Review Call with pricing options, endorsements, and requested changes
* Logging an Underwriting Follow-Up to track required documents or clarifications
* Scheduling a Policy Renewal Outreach <code class="expression">space.vars.activity</code> tied to expiration dates and retention workflows

**How Activities help:**

* Provide a complete, auditable history of policyholder interactions for regulatory and internal review
* Standardize engagement data across agents to ensure consistent policy handling
* Drive <code class="expression">space.vars.automations</code> (e.g., underwriting reminders, renewal notices, lapse prevention workflows)
* Synchronize policyholder interaction data across CRM, underwriting systems, and external platforms via APIs and webhook events
  {% endtab %}

{% tab title="Healthcare" %}

#### Healthcare Teams Managing Beneficiary Interactions

Enrollment and care-management workflows use <code class="expression">space.vars.activities</code> to capture structured <code class="expression">space.vars.entities</code> of every interaction with a member, supporting compliance, consistency, and automation.

**Examples include:**

* Logging an Initial Coverage Consultation with plan options discussed
* Recording a Follow-Up <code class="expression">space.vars.activity</code> confirming doctors, prescriptions, and pharmacies
* Logging a Plan Recommendation Review meeting with documented outcomes
* Scheduling an Enrollment Deadline Reminder <code class="expression">space.vars.activity</code> tied to cutoff dates

**How Activities help:**

* Provide a complete audit trail required for regulatory and CMS compliance
* Standardize interaction data across agents for consistent member guidance
* Drive automations (e.g., follow-up reminders, missing-document alerts, enrollment workflows)
* Keep beneficiary <code class="expression">space.vars.entities</code> synchronized across systems using webhook events&#x20;
  {% endtab %}

{% tab title="Financial Services" %}

#### Financial Services Teams Managing Client Interactions

Financial advisory workflows rely on <code class="expression">space.vars.activities</code> to create compliant, structured <code class="expression">space.vars.entities</code> of every client interaction that influences investment strategy or regulatory reporting.

**Examples include:**

* Logging a Quarterly Portfolio Review with performance notes and agreed actions
* Scheduling a Risk Tolerance Review <code class="expression">space.vars.activity</code> triggered by life-event changes
* Recording an in-person Account Update <code class="expression">space.vars.activity</code> with required verification fields
* Logging a Follow-Up <code class="expression">space.vars.activity</code> after sending recommendations or disclosures

**How Activities help:**

* Create a chronological audit trail required for compliance and advisory oversight
* Standardize client interaction data used in suitability checks and planning workflows
* Trigger <code class="expression">space.vars.automations</code> for follow-ups, document requests, or portfolio review cycles
* Sync engagement data to external advisory platforms via webhooks
  {% endtab %}
  {% endtabs %}

***

## What's Next?

Continue to the [Activities Data Model](/docs/concepts/activities/activities-data-model.md) to understand how <code class="expression">space.vars.activities</code> are represented structurally in <code class="expression">space.vars.Kizen\_company\_name</code>, including:

* The core <code class="expression">space.vars.activity</code> fields and field types
* How <code class="expression">space.vars.activity</code> <code class="expression">space.vars.objects</code> define schemas and associations
* How <code class="expression">space.vars.activities</code> relate to <code class="expression">space.vars.contacts</code> and other <code class="expression">space.vars.entities</code>
* How <code class="expression">space.vars.activity</code> data is stored and referenced across the platform

Understanding the data model is essential before working with <code class="expression">space.vars.activity</code> permissions, APIs, <code class="expression">space.vars.automations</code>, or integrations.

<details>

<summary>Related Topics</summary>

* [Activities](/docs/concepts/activities.md)
* [Activities Data Model](/docs/concepts/activities/activities-data-model.md)
* [Activity Permissions](/docs/concepts/activities/activity-permissions.md)
* [Advanced Activity Rules](/docs/concepts/activities/advanced-activity-rules.md)
* [Activities API & Webhooks](/docs/concepts/activities/activities-api-and-webhooks.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/concepts/activities/activities-core-concepts.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.