# Starting Agentic Workflows

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

**Purpose:** Documents every supported method for initiating an <code class="expression">space.vars.automation</code> in <code class="expression">space.vars.Kizen\_company\_name</code> and explains the key behaviors and configuration considerations for each, so readers can choose the right initiation approach before configuring triggers or designing execution logic.
{% endhint %}

## Overview

<code class="expression">space.vars.automations</code> in <code class="expression">space.vars.Kizen\_company\_name</code> can be initiated in several ways: by a user acting directly on a <code class="expression">space.vars.entity</code>, on a scheduled date and time, in response to a data event or external signal, or by another <code class="expression">space.vars.automation</code>. The method you choose determines when an execution begins, what <code class="expression">space.vars.entity</code> context is available at runtime, and how the resulting execution is identified and tracked.

Understanding the available initiation methods is the first step toward designing <code class="expression">space.vars.automations</code> that start at the right time, in the right context, and for the right reasons.

***

## Manual & User-Initiated Starts

<code class="expression">space.vars.automations</code> can be started manually by any authorized user using the following methods.

| Method                                     | What It Does                                                                                                                                                                                                                                       | Notes                                                                                                                                                          |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Manual Trigger**                         | Starts an execution on demand from a <code class="expression">space.vars.entity</code>                                                                                                                                                             | Present on every <code class="expression">space.vars.automation</code>; cannot be removed                                                                      |
| **Start from a Record**                    | Initiates an execution directly from the <code class="expression">space.vars.entity</code> interface                                                                                                                                               | Starts immediately in the context of that <code class="expression">space.vars.entity</code>. See [Records](/docs/concepts/objects/records.md)                  |
| **Bulk Start via Modify Agentic Workflow** | Starts an <code class="expression">space.vars.automation</code> across multiple <code class="expression">space.vars.entities</code> simultaneously using the Modify <code class="expression">space.vars.automation</code> bulk action              | Appears in execution history as a manual trigger initiated by the user. See [Bulk Start: Execution History Behavior](#bulk-start-execution-history-behavior)   |
| **Layout Action Block**                    | Surfaces a curated set of <code class="expression">space.vars.automations</code> on a <code class="expression">space.vars.entity</code> layout so users can initiate them directly from the <code class="expression">space.vars.entity</code> view | Requires layout configuration. See [Record Layout Customization](/docs/concepts/objects/object-configuration/object-layout-customization.md#record-layout-tab) |
| **Resume Paused Toggle**                   | Controls whether existing paused executions are resumed or whether new executions are created when starting manually or in bulk                                                                                                                    | Toggle is available at the time of start                                                                                                                       |
| **Reactivation**                           | Restarts trigger listening when an inactive <code class="expression">space.vars.automation</code> is turned active again                                                                                                                           | Does not process events that occurred while inactive. See [No Backlog Behavior on Reactivation](#no-backlog-behavior-on-reactivation)                          |

### Bulk Start: Execution History Behavior

When an <code class="expression">space.vars.automation</code> is started via the Modify <code class="expression">space.vars.automation</code> bulk action, each resulting execution appears in execution history as a manual trigger initiated by the user, not as a distinct bulk trigger type. If you are auditing executions or troubleshooting unexpected runs, bulk-initiated executions are attributed to the user who performed the action and are indistinguishable in the execution list from individual manual starts.

### No Backlog Behavior on Reactivation

When an <code class="expression">space.vars.automation</code> is deactivated, it stops listening for triggers entirely. Reactivating an <code class="expression">space.vars.automation</code> does not cause it to retroactively process <code class="expression">space.vars.entities</code> or events that occurred while it was inactive. There is no backlog catchup. The <code class="expression">space.vars.automation</code> begins listening from the moment it becomes active again.

This is a firm behavioral boundary, not a configuration option. If you need to run an <code class="expression">space.vars.automation</code> against <code class="expression">space.vars.entities</code> that were not processed during an inactive period, use a bulk start to target them manually after reactivating.

***

## Scheduled & Event-Based Starts

Event-based triggers fire when a specific action occurs on a <code class="expression">space.vars.entity</code>. For more information on these types of starts see, [Action Based Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/action-based-triggers.md)**.**

Scheduled triggers fire based on time rather than a user action or data change. For more information on these types of starts see, [Scheduled Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/scheduled-triggers.md)**.**

***

## Automation-to-Automation Starts

An <code class="expression">space.vars.automation</code> can include a Start <code class="expression">space.vars.automation</code> action that initiates another <code class="expression">space.vars.automation</code>. This step can target an <code class="expression">space.vars.automation</code> on the same <code class="expression">space.vars.entity</code>, on a related <code class="expression">space.vars.entity</code>, on a <code class="expression">space.vars.entity</code> identified by a variable, or a global <code class="expression">space.vars.automation</code> with no <code class="expression">space.vars.entity</code> context. This pattern is useful for chaining specialized <code class="expression">space.vars.automations</code> together, separating concerns across distinct <code class="expression">space.vars.automation</code> configurations, or handing off execution once a specific phase of a <code class="expression">space.vars.workflow</code> is complete.

When an <code class="expression">space.vars.automation</code> is started this way, the resulting execution appears in execution history identifying both the called and calling <code class="expression">space.vars.automations</code>, formatted as the called <code class="expression">space.vars.automation</code> name started by the calling <code class="expression">space.vars.automation</code> name. This makes it distinguishable from a manual trigger or an event-based trigger, and provides a clear audit trail showing which <code class="expression">space.vars.automation</code> initiated the execution and which <code class="expression">space.vars.automation</code> was started as a result.

{% hint style="info" %}
**Note:** The ability to pass variable overrides when starting an <code class="expression">space.vars.automation</code> from another <code class="expression">space.vars.automation</code> is a planned capability and is not yet supported. Variable overrides would allow the initiated execution to be seeded with data from the calling <code class="expression">space.vars.automation</code>'s context.
{% endhint %}

***

## What's Next

The next step is a deeper look at <code class="expression">space.vars.automation</code> Triggers, including how each trigger type evaluates conditions, how timing and throttling affect execution, and the rules that govern each trigger's behavior. For more information, continue to the [Agentic Workflow Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers.md) topic.

<details>

<summary>Related Topics</summary>

* [Agentic Workflow Core Concepts](/docs/concepts/agentic-workflows/agentic-workflow-core-concepts.md)
* [Agentic Workflow Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers.md)
* [Record Layout Customization](/docs/concepts/objects/object-configuration/object-layout-customization.md#record-layout-tab)
* Webhook Trigger (POST) **(Topic Coming Soon)**
* Webhook Trigger (GET) **(Topic Coming Soon)**

</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/starting-agentic-workflows.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.