# Action-Based Triggers

{% hint style="success" %}
**Audience:** Administrators, Solution Architects, and Developers

**Purpose:** Documents each action-based trigger type in <code class="expression">space.vars.Kizen\_company\_name</code>: what it does, when it fires, and the behavioral details that affect how <code class="expression">space.vars.automations</code> respond to <code class="expression">space.vars.entity</code> changes and user actions.
{% endhint %}

## Overview

Action-based triggers fire in response to a data change or user action on a <code class="expression">space.vars.entity</code>. When the specified event occurs, <code class="expression">space.vars.Kizen\_company\_name</code> queues a trigger evaluation. If the trigger conditions are satisfied it then initiates a new <code class="expression">space.vars.automation</code> execution.

### Activity Logged

This trigger fires when an <code class="expression">space.vars.activity</code> of a selected type is logged on a <code class="expression">space.vars.entity</code>.&#x20;

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

Each trigger configuration listens for a single <code class="expression">space.vars.activity</code> type. To respond to multiple <code class="expression">space.vars.activity</code> types on the same <code class="expression">space.vars.automation</code>, configure a separate trigger for each.

{% hint style="info" %}
**Note**: Scheduling a future <code class="expression">space.vars.activity</code> task does not fire this trigger. It evaluates only at the moment an <code class="expression">space.vars.activity</code> is marked as completed and logged.
{% endhint %}

### New Record Created

Fires when a new <code class="expression">space.vars.entity</code> is created. Can be configured to fire on creation, unarchive, or both.

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

Field values available at trigger time reflect only what was present at the moment of creation. Values populated by subsequent actions or <code class="expression">space.vars.automations</code> will not be available.

### Field Updated

Fires when a specified field's value changes on a <code class="expression">space.vars.entity</code>.

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

By default, the trigger fires on any change to the field. You can narrow this by configuring from and to values. For example, only when a Status field transitions from *Prospect* to *Qualified*. Transitions to or from a blank value are supported and can be explicitly targeted.

An optional trigger on create setting causes the trigger to evaluate at <code class="expression">space.vars.entity</code> creation. If no from/to values are configured, enabling this option will cause the trigger to fire on every new <code class="expression">space.vars.entity</code> regardless of the field's initial value.

### Stage Updated

Fires when a <code class="expression">space.vars.entity</code> moves from one workflow stage to another.&#x20;

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

This trigger is only available on <code class="expression">space.vars.object</code> <code class="expression">space.vars.automations</code>; it is not available in <code class="expression">space.vars.contact</code>, Global, or standard <code class="expression">space.vars.object</code> <code class="expression">space.vars.automation</code> contexts.

### Form Submitted

Fires when a specific form associated with the <code class="expression">space.vars.entity</code> is submitted.&#x20;

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

Scoped to a single form per trigger configuration. It does not fire for all form submissions on the <code class="expression">space.vars.entity</code>.

### Survey Submitted

Fires when a specific survey associated with the <code class="expression">space.vars.entity</code> is submitted.

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

Behaves consistently with Form Submitted, and is scoped to a single survey per trigger configuration.

### Email Received

Fires when an email is received from a <code class="expression">space.vars.contact</code>.&#x20;

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

This trigger is only available on <code class="expression">space.vars.contact</code> <code class="expression">space.vars.automations</code>. It is not available in <code class="expression">space.vars.workflow</code>, Global, or standard <code class="expression">space.vars.object</code> <code class="expression">space.vars.automation</code> contexts.

### Tag Added / Tag Removed

Fires when a specific tag is added to or removed from a <code class="expression">space.vars.entity</code>.&#x20;

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

Tag Added and Tag Removed are separate trigger types. To respond to both directions of a tag change on the same <code class="expression">space.vars.automation</code>, configure one trigger of each type.

***

## What's Next?

Continue to [Scheduled Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/scheduled-triggers.md) to understand the trigger types that fire based on time or date field values.

<details>

<summary>Related Topics</summary>

* [Agentic Workflow Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers.md)
* [Scheduled Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/scheduled-triggers.md)
* [Webhook Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/webhook-triggers.md)
* [Agentic Workflow Code Step](/docs/concepts/agentic-workflows/automation-code-steps.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/agentic-workflows/agentic-workflow-triggers/action-based-triggers.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.