Agentic Workflow Related Object Actions
Audience: Administrators, Developers, Solution Architects
Purpose: Complete reference for the related Object action types available in Kizen Agentic Workflows, including how to create and modify related Records, send communications to related Contacts, and archive Records from within an execution.
Overview
Related Object actions operate on Records associated with the context Record. Use them to create new Records in related Objects, update field values on related Records Agentic Workflow beyond the context, send email and text messages to related Contacts, and archive Records when they are no longer active. These actions extend the reach of an Record to the broader data model.
Note: For error handling, see Agentic Workflow Error Handling.
Create Entity
The Create Entity action creates a new Record in a specified Object.
Create New Entity in the Following Object: Select the Object in which the new Record will be created. All Objects in the business are listed.
New Entity Name: Set the name for the new Record. The field supports merge fields. Use + INSERT MERGE FIELD to insert values from context Record fields, variables, or other sources dynamically.
Duplicate Handling: Two separate settings control what happens if a Record 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 Record is created
Create New Record with "(copy #)": creates the Record with a copy suffix
If an archived Record exists with the same name:
Delete Archived Record and Create: deletes the archived Record and creates a new one
Unarchive Existing Record: restores the archived Record instead of creating a new one
Create New Record with "(copy #)": creates a new Record with a copy suffix, leaving the archived Record in place
Error and Don't Create: the step fails and no Record is created
Modify Related Entity
The Modify Related Entity action updates field values on a related Record rather than the context Record.
Related Object Information: Under Choose Object to Modify, use the Choose Related Object dropdown to select the related Object whose Records will be updated. Only Objects with a defined relationship to the context Object are available.
Send Email to Related Contact(s)
The Send Email to Related Contact(s) action sends an email to a Contact identified through a relationship field on the context Record.
Send Email to Related Contact(s) in Field: Use the Choose Related Contact dropdown to select the Contact relationship field to resolve the recipient from. Fields are grouped by Object. 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 Record, regardless of role
Last Active Team Member (Specific Role): CC the most recently active team member on the Record who holds a specified role
Owner: CC the Record 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 Record
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 Record.
Send Email to Related Contact(s) in Field: Use the Choose Related Contact dropdown to select the Contact relationship field to resolve the recipient from. Fields are grouped by Object. 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 Record fields or variables.
The body supports up to 10 message segments of 153 characters each, for a maximum of 1,530 total characters.
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 Record(s) action archives one or more Records.
Under Choose Record Source, select one of three options to identify the Record(s) to archive:
This Record (execution context): Archives the current context Record
Related Object Record(s): Archives one or more related Records; use the Choose Related Object dropdown to select the relationship to traverse
Agentic Workflow Variable: Archives a Record identified by an Agentic Workflow variable
All executions running against the archived Record(s) will be immediately canceled when this action step is processed.
This warning is displayed in the UI regardless of which Record source is selected. If your Agentic Workflowarchives the context Record mid-execution, subsequent steps in that execution will not run.
If other Agentic Workflows are running against the same Record simultaneously, those executions will also be canceled. Design archiving logic carefully and account for this side effect when sequencing steps.
Key Use Cases
Related Object actions are applicable across any Workflows that requires work to be performed on Records other than the context Record. The following examples illustrate common patterns in three industries where cross-object Agentic Workflow is a core operational requirement.
Industry Examples
Insurance Workflows frequently require actions to be taken on related Records, such as creating a claim Record when a policy event occurs or archiving a related Contact Record when coverage lapses.
Examples include:
Using Create Entity to create a new claim Record in the Claims Object when a policy Agentic Workflow 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 Record 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 Record when a policy is terminated
How related Object actions help:
Create downstream Records automatically when qualifying events occur, without requiring manual data entry across Objects
Keep related Record data current by writing field updates to associated Records as part of the same Agentic Workflow execution
Communicate directly with Contacts associated with the context Record without requiring a separate contact Agentic Workflow
Manage the full lifecycle of related Records, including archiving, from within a single Agentic Workflow
Healthcare workflows often require actions across multiple related Objects, including patient Records, provider Records, authorization Records, and Contact Records within a single automated process.
Examples include:
Using Create Entity to create a new authorization request Record 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 Record when a patient is reassigned
Using Send Text To Related Contact(s) to send an appointment reminder to the primary contact on a patient Record
Using Archive Record(s) to archive a related referral Record when the referral is closed or expired
How related object actions help:
Automate the creation of downstream Records, such as authorizations, referrals, and appointments, at the precise point in a workflow when they are needed
Keep provider, appointment, and referral Records current by writing updates to related Records as part of the same execution
Reach contacts associated with the context Record directly, without requiring a separate Contact-based automation
Maintain clean data by archiving related Records when they reach a terminal state
Financial services workflows require actions across loan, account, Contact, and compliance records throughout the origination, onboarding, and servicing lifecycle.
Examples include:
Using Create Entity to create a new compliance review Record in the Reviews Object when a loan application Agentic Workflow reaches the underwriting stage
Using Modify Related Entity to update the account status field on a related account Record 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 Record
Using Archive Record(s) to archive a related co-applicant Record when an application is withdrawn
How related Object actions help:
Create compliance, review, and servicing Records automatically at the point in the workflow when they are required
Keep account and servicing Records current by writing status and classification updates to related Records as part of the same execution
Communicate with borrowers and account holders associated with the context Record without requiring a separate Contact Agentic Workflow
Archive related Records at terminal states to keep data models clean and reporting accurate
What's Next?
Continue to Team Actions to learn how to send email and text notifications to team members and assign team members to a Record from within an Agentic Workflow execution.
Last updated
Was this helpful?