> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-related-object-actions.md).

# Agentic Workflow Related Object Actions

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

**Purpose:** Complete reference for the related <code class="expression">space.vars.object</code> action types available in <code class="expression">space.vars.Kizen\_company\_name</code> <code class="expression">space.vars.automations</code>, including how to create and modify related <code class="expression">space.vars.entities</code>, send communications to related <code class="expression">space.vars.contacts</code>, and archive <code class="expression">space.vars.entities</code> from within an execution.
{% endhint %}

## Overview

Related <code class="expression">space.vars.object</code> actions operate on <code class="expression">space.vars.entities</code> associated with the context <code class="expression">space.vars.entity</code>. Use them to create new <code class="expression">space.vars.entities</code> in related <code class="expression">space.vars.objects</code>, update field values on related <code class="expression">space.vars.entities</code> <code class="expression">space.vars.automation</code> beyond the context, send email and text messages to related <code class="expression">space.vars.contacts</code>, and archive <code class="expression">space.vars.entities</code> when they are no longer active. These actions extend the reach of an <code class="expression">space.vars.entity</code> to the broader data model.

{% hint style="info" %}
**Note:** For error handling, see [Agentic Workflow Error Handling](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-error-handling.md).
{% endhint %}

***

## Create Entity

The Create Entity action creates a new <code class="expression">space.vars.entity</code> in a specified <code class="expression">space.vars.object</code>.

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

**Create New Entity in the Following Object:** Select the <code class="expression">space.vars.object</code> in which the new <code class="expression">space.vars.entity</code> will be created. All <code class="expression">space.vars.objects</code> in the business are listed.

**New Entity Name:** Set the name for the new <code class="expression">space.vars.entity</code>. The field supports merge fields. Use **+ INSERT MERGE FIELD** to insert values from context <code class="expression">space.vars.entity</code> fields, variables, or other sources dynamically.

**Duplicate Handling:** Two separate settings control what happens if a <code class="expression">space.vars.entity</code> with the same name already exists.

*If an active Record exists with the same name:*

* **Error and Don't Create:** the step fails and no <code class="expression">space.vars.entity</code> is created
* **Create New Record with "(copy #)":** creates the <code class="expression">space.vars.entity</code> with a copy suffix

*If an archived Record exists with the same name:*

* **Delete Archived Record and Create:** deletes the archived <code class="expression">space.vars.entity</code> and creates a new one
* **Unarchive Existing Record:** restores the archived <code class="expression">space.vars.entity</code> instead of creating a new one
* **Create New Record with "(copy #)":** creates a new <code class="expression">space.vars.entity</code> with a copy suffix, leaving the archived <code class="expression">space.vars.entity</code> in place
* **Error and Don't Create:** the step fails and no <code class="expression">space.vars.entity</code> is created

## Modify Related Entity

The Modify Related Entity action updates field values on a related <code class="expression">space.vars.entity</code> rather than the context <code class="expression">space.vars.entity</code>.

<div data-with-frame="true"><figure><img src="/files/4fhjErnDnPgqnGLdWyEg" alt="" width="259"><figcaption></figcaption></figure></div>

**Related Object Information:** Under **Choose Object to Modify**, use the **Choose Related Object** dropdown to select the related <code class="expression">space.vars.object</code> whose <code class="expression">space.vars.entities</code> will be updated. Only <code class="expression">space.vars.objects</code> with a defined relationship to the context <code class="expression">space.vars.object</code> are available.

## Send Email to Related Contact(s)

The Send Email to Related <code class="expression">space.vars.contact</code>(s) action sends an email to a <code class="expression">space.vars.contact</code> identified through a relationship field on the context <code class="expression">space.vars.entity</code>.

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

**Send Email to Related Contact(s) in Field:** Use the **Choose Related Contact** dropdown to select the <code class="expression">space.vars.contact</code> relationship field to resolve the recipient from. Fields are grouped by <code class="expression">space.vars.object</code>. For example, a **Contacts** group may contain options such as **Primary Contact Record**.

**CC Team Members:** Optionally CC one or more team members on the email. The **CC Team Members** dropdown offers the following options:

* **None:** no team members are CC'd
* **Last Active Team Member (Any Role):** CC the most recently active team member on the <code class="expression">space.vars.entity</code>, regardless of role
* **Last Active Team Member (Specific Role):** CC the most recently active team member on the <code class="expression">space.vars.entity</code> who holds a specified role
* **Owner:** CC the <code class="expression">space.vars.entity</code> owner
* **Specific Team Members:** CC one or more individually selected team members
* **Custom Team Selector Field:** CC a team member resolved from a team selector field on the <code class="expression">space.vars.entity</code>

**Choose Email To Send:** Select an existing email template using **CHOOSE EMAIL FROM LIBRARY**, or compose a new one using **CREATE NEW EMAIL**.

* Based on your email account type, a daily quota might apply to emails sent via the selected integrated inbox.

## Send Text To Related Contact(s)

The Send Text To Related Contact(s) action sends a text message to a contact identified through a relationship field on the context <code class="expression">space.vars.entity</code>.

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

**Send Email to Related Contact(s) in Field:** Use the **Choose Related Contact** dropdown to select the <code class="expression">space.vars.contact</code> relationship field to resolve the recipient from. Fields are grouped by <code class="expression">space.vars.object</code>. For example, a **Contacts** group may contain options such as **Primary Contact Record**.

**Text Message Body:** Compose the message in the **Text Message Body** field. Use **+ INSERT MERGE FIELD** to insert dynamic values from context <code class="expression">space.vars.entity</code> fields or variables.&#x20;

* The body supports up to 10 message segments of 153 characters each, for a maximum of 1,530 total characters.&#x20;
* The character counter below the body field tracks remaining characters in the current segment and total characters used.
* Text message broadcasts require a text messaging provider to be configured in the business settings before this action can send successfully.

## Archive Record(s)

The Archive <code class="expression">space.vars.entity</code>(s) action archives one or more <code class="expression">space.vars.entities</code>.&#x20;

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

Under **Choose Record Source**, select one of three options to identify the <code class="expression">space.vars.entity</code>(s) to archive:

* **This Record (execution context):** Archives the current context <code class="expression">space.vars.entity</code>
* **Related Object Record(s):** Archives one or more related <code class="expression">space.vars.entities</code>; use the **Choose Related Object** dropdown to select the relationship to traverse
* **Agentic Workflow Variable:** Archives a <code class="expression">space.vars.entity</code> identified by an <code class="expression">space.vars.automation</code> variable

*All executions running against the archived Record(s) will be immediately canceled when this action step is processed.*&#x20;

This warning is displayed in the UI regardless of which <code class="expression">space.vars.entity</code> source is selected. If your <code class="expression">space.vars.automation</code>archives the context <code class="expression">space.vars.entity</code> mid-execution, subsequent steps in that execution will not run.&#x20;

If other <code class="expression">space.vars.automations</code> are running against the same <code class="expression">space.vars.entity</code> simultaneously, those executions will also be canceled. Design archiving logic carefully and account for this side effect when sequencing steps.

***

## Key Use Cases

Related <code class="expression">space.vars.object</code> actions are applicable across any <code class="expression">space.vars.workflows</code> that requires work to be performed on <code class="expression">space.vars.entities</code> other than the context <code class="expression">space.vars.entity</code>. The following examples illustrate common patterns in three industries where cross-object <code class="expression">space.vars.automation</code> is a core operational requirement.

### Industry Examples

{% tabs %}
{% tab title="Insurance" %}
Insurance <code class="expression">space.vars.workflows</code> frequently require actions to be taken on related <code class="expression">space.vars.entities</code>, such as creating a claim <code class="expression">space.vars.entity</code> when a policy event occurs or archiving a related <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> when coverage lapses.

Examples include:

* Using **Create Entity** to create a new claim <code class="expression">space.vars.entity</code> in the Claims <code class="expression">space.vars.object</code> when a policy <code class="expression">space.vars.automation</code> detects a qualifying loss event, with duplicate handling configured to error and not create if an active claim already exists
* Using **Modify Related Entity** to update the status field on a related agent <code class="expression">space.vars.entity</code> when a policy is assigned to a new producer
* Using **Send Email to Related Contact(s**) to notify the primary insured contact when a policy renewal is processed
* Using **Archive Record(s)** to archive a related beneficiary <code class="expression">space.vars.entity</code> when a policy is terminated

How related <code class="expression">space.vars.object</code> actions help:

* Create downstream <code class="expression">space.vars.entities</code> automatically when qualifying events occur, without requiring manual data entry across <code class="expression">space.vars.objects</code>
* Keep related <code class="expression">space.vars.entity</code> data current by writing field updates to associated <code class="expression">space.vars.entities</code> as part of the same <code class="expression">space.vars.automation</code> execution
* Communicate directly with <code class="expression">space.vars.contacts</code> associated with the context <code class="expression">space.vars.entity</code> without requiring a separate contact <code class="expression">space.vars.automation</code>
* Manage the full lifecycle of related <code class="expression">space.vars.entities</code>, including archiving, from within a single <code class="expression">space.vars.automation</code>
  {% endtab %}

{% tab title="Healthcare" %}
Healthcare workflows often require actions across multiple related <code class="expression">space.vars.objects</code>, including patient <code class="expression">space.vars.entities</code>, provider <code class="expression">space.vars.entities</code>, authorization <code class="expression">space.vars.entities</code>, and <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> within a single automated process.

Examples include:

* Using **Create Entity** to create a new authorization request <code class="expression">space.vars.entity</code> in the Authorizations object when a patient intake automation reaches a qualifying clinical stage
* Using **Modify Related Entity** to update the assigned provider field on a related appointment <code class="expression">space.vars.entity</code> when a patient is reassigned
* Using **Send Text To Related Contact(s)** to send an appointment reminder to the primary contact on a patient <code class="expression">space.vars.entity</code>
* Using **Archive Record(s)** to archive a related referral <code class="expression">space.vars.entity</code> when the referral is closed or expired

How related object actions help:

* Automate the creation of downstream <code class="expression">space.vars.entities</code>, such as authorizations, referrals, and appointments, at the precise point in a workflow when they are needed
* Keep provider, appointment, and referral <code class="expression">space.vars.entities</code> current by writing updates to related <code class="expression">space.vars.entities</code> as part of the same execution
* Reach contacts associated with the context <code class="expression">space.vars.entity</code> directly, without requiring a separate <code class="expression">space.vars.contact</code>-based automation
* Maintain clean data by archiving related <code class="expression">space.vars.entities</code> when they reach a terminal state
  {% endtab %}

{% tab title="Financial Services" %}
Financial services workflows require actions across loan, account, <code class="expression">space.vars.contact</code>, and compliance records throughout the origination, onboarding, and servicing lifecycle.

Examples include:

* Using **Create Entity** to create a new compliance review <code class="expression">space.vars.entity</code> in the Reviews <code class="expression">space.vars.object</code> when a loan application <code class="expression">space.vars.automation</code> reaches the underwriting stage
* Using **Modify Related Entity** to update the account status field on a related account <code class="expression">space.vars.entity</code> when a loan is funded
* Using **Send Email to Related Contact(s)** to send a closing disclosure to the primary borrower contact on a loan application <code class="expression">space.vars.entity</code>
* Using **Archive Record(s)** to archive a related co-applicant <code class="expression">space.vars.entity</code> when an application is withdrawn

How related <code class="expression">space.vars.object</code> actions help:

* Create compliance, review, and servicing <code class="expression">space.vars.entities</code> automatically at the point in the workflow when they are required
* Keep account and servicing <code class="expression">space.vars.entities</code> current by writing status and classification updates to related <code class="expression">space.vars.entities</code> as part of the same execution
* Communicate with borrowers and account holders associated with the context <code class="expression">space.vars.entity</code> without requiring a separate <code class="expression">space.vars.contact</code> <code class="expression">space.vars.automation</code>
* Archive related <code class="expression">space.vars.entities</code> at terminal states to keep data models clean and reporting accurate
  {% endtab %}
  {% endtabs %}

***

## What's Next?

Continue to [Team Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-team-actions.md) to learn how to send email and text notifications to team members and assign team members to a <code class="expression">space.vars.entity</code> from within an <code class="expression">space.vars.automation</code> execution.

<details>

<summary>Related Topics</summary>

* [Automation Control Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-control-actions.md)
* [Field Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-field-actions.md)
* [Team Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-team-actions.md)
* [Integration Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-integration-actions.md)
* [Messages Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-messages-actions.md)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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-actions/agentic-workflow-related-object-actions.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.