> 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-activity-actions.md). # Agentic Workflow Activity Actions {% hint style="success" %} **Audience:** Administrators, Developers, Solution Architects **Purpose**: A reference for the space.vars.activity action types available in space.vars.Kizen\_company\_name space.vars.automations: how to schedule and delete space.vars.activities on a space.vars.entity, and what configuration options are available for assignment, due dates, and notifications. {% endhint %} ## Overview space.vars.activity actions automate the creation and removal of scheduled space.vars.activities on the space.vars.entity. Use them to assign follow-up tasks, reminders, and other work items to team members as part of a larger space.vars.automation space.vars.workflow without manual intervention. {% 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 %} *** ## Schedule Activity The Schedule space.vars.activity action creates a scheduled space.vars.activity on the context space.vars.entity. It is one of the more configurable action types in the platform, with a full set of assignment, due date, association, and notification options.

**Assignment rules** The **Assign To** dropdown offers the following assignment types: * **Round Robin (Team Member of Any Role):** Cycles assignment across all verified employees in the business, regardless of role * **Round Robin (Team Member of Specific Role):** Cycles assignment across all team members who hold a specified role * **Round Robin (Select Team Members):** Cycles assignment across a manually selected list of team members * **Owner:** Assigns the space.vars.activity to whoever currently owns the context space.vars.entity at the time the step executes * **Specific Team Member:** Assigns to a single named team member selected at design time * **Custom Team Selector Field:** Resolves the assignee from a team member field on the context space.vars.entity * **Last Active Team Member (Any Role):** Assigns to the most recently active team member on the space.vars.entity, regardless of role * **Last Active Team Member (Specific Role):** Assigns to the most recently active team member on the space.vars.entity who holds a specified role * **Specific Role:** Assigns to a team member of a specified role * **Team Member From Variable:** Resolves the assignee from a variable holding a team member value Round robin assignment tracking is maintained per space.vars.automation step, not globally across the business or across other steps or space.vars.automations. Two separate Schedule space.vars.activity steps, even within the same space.vars.automation, each maintain their own independent round robin sequence. **Due date configuration:** The **Assignment Timeframe** dropdown controls when the space.vars.activity is due: * **Immediately:** the space.vars.activity is due at the time the step executes * **With Delay:** the due date is offset by a specified duration from the time of execution * **On or Around Date:** the due date is set to a specified date field on the space.vars.entity, with an optional offset * **On or Around Date/Time Variable:** the due date is resolved from a date/time variable, with an optional offset **Notes:** Freeform note content can be attached to the space.vars.activity. The notes field supports merge fields sourced from variables, context space.vars.entity attributes, or business fields. **Notifications:** Use **+ Add Notification** to configure notification behavior for the assigned team member when the space.vars.activity is created. ## Delete Scheduled Activities The Delete Scheduled space.vars.activities action deletes all scheduled space.vars.activities of a specified type associated with the context space.vars.entity.

This is useful for clearing pending space.vars.activities when a record reaches a state that makes them irrelevant. For example, removing open follow-up reminders when an opportunity closes or a contact opts out. The deletion is scoped to the context space.vars.entity and the selected space.vars.activity type; space.vars.activities on other space.vars.entities are not affected. **Activity selection:** Use the **Find Activities** search field under **Delete Scheduled Activities** to locate and select the space.vars.activity type to delete. All space.vars.activity types configured for the business are available in the list. *** ## Key Use Cases space.vars.activity actions are applicable across any space.vars.workflow that requires structured task assignment and follow-up. The following examples illustrate common patterns in three industries where consistent, auditable space.vars.activity management is a core operational requirement. #### Industry Examples {% tabs %} {% tab title="Insurance" %} Insurance space.vars.workflows use space.vars.activity actions to automate task creation across underwriting, claims, renewals, and compliance while ensuring that structured follow-up work is assigned and tracked at every stage of the policy and claims lifecycle. **Examples include:** * Scheduling a claims review space.vars.activity assigned to the adjuster identified by a team selector field on the claim space.vars.entity, due within a configured SLA window from the date of submission * Scheduling a renewal outreach space.vars.activity assigned via round robin to the retention team, due on or around the policy expiration date field * Scheduling an underwriting follow-up space.vars.activity when a required document field is left blank at submission, assigned to the underwriter who owns the space.vars.entity * Deleting all pending follow-up space.vars.activities on a policy space.vars.entity when the policy is marked as canceled or non-renewed **How Activity actions help:** * Automate task creation at key lifecycle events such as new submissions, claim filings, renewal windows, without relying on manual assignment * Enforce SLA-aligned due dates by tying space.vars.activity timeframes to date fields on the space.vars.entity rather than fixed offsets * Keep team queues clean by removing irrelevant space.vars.activities when a space.vars.entity reaches a terminal state * Provide a structured, assignable work item at every stage of the policy or claims process that can be tracked, reported on, and audited {% endtab %} {% tab title="Healthcare" %} Healthcare organizations use space.vars.activity actions to automate task assignment and follow-up scheduling across the patient lifecycle while ensuring the right team member is assigned the right work at the right time without manual coordination. **Examples include:** * Scheduling an initial intake follow-up space.vars.activity assigned via round robin to the next available care coordinator when a new patient record is created * Scheduling a post-discharge check-in space.vars.activity assigned to the patient's primary care manager, due three days after a discharge date field is set * Scheduling a prior authorization follow-up assigned to the last active team member on the record when an authorization request is submitted * Deleting all pending outreach space.vars.activities when a patient record is marked as inactive or transferred to another provider **How Activity actions help:** * Ensure follow-up tasks are created and assigned automatically, reducing the risk of patients falling through the gaps between care touchpoints * Distribute task assignment across care teams using round robin logic without requiring manual queue management * Align space.vars.activity due dates to clinical milestones (admission dates, discharge dates, authorization deadlines) using date field offsets. * Remove stale tasks automatically when a space.vars.entitys status changes, keeping team queues accurate and actionable {% endtab %} {% tab title="Financial Services" %} Financial services organizations use space.vars.activity actions to automate task assignment across relationship management, loan origination, compliance reviews, and client onboarding — ensuring that time-sensitive work is created, assigned, and tracked without manual intervention. **Examples include:** * Scheduling an annual portfolio review space.vars.activity assigned to the relationship manager who owns the account, due on or around the client's scheduled review date field * Scheduling a loan document follow-up space.vars.activity assigned via round robin to the processing team when an application is submitted with missing documentation * Scheduling a KYC review space.vars.activity assigned to the compliance officer identified by a field on the account space.vars.entity, due within a regulatory timeframe from account opening * Deleting all pending outreach space.vars.activities on a loan application space.vars.entity when the application is closed, whether funded, declined, or withdrawn. **How Activity actions help:** * Align task due dates to client-specific milestones (review dates, maturity dates, regulatory deadlines) using date field and variable-based timeframe configuration. * Distribute work across relationship managers, processors, and compliance staff using role-based or round robin assignment without manual queue management * Ensure that time-sensitive compliance and review tasks are created automatically when triggering conditions are met, reducing the risk of missed deadlines * Remove stale tasks automatically when an application or account reaches a terminal state, keeping team workloads accurate and auditable {% endtab %} {% endtabs %} *** ## What's Next? Continue to [Agentic Workflow Control Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-control-actions.md) to learn how to start, pause, cancel, and redirect space.vars.automations from within an execution. This includes how to target related space.vars.entities, manage paused executions, and control terminal states.