> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Automations

> An overview of automation types in Operations Manager and how to create, configure, and manage them.

An automation is the container in Operations Manager that binds a resource to triggers and controls who can run it. When a trigger fires, Operations Manager runs the associated resource.

Each automation has one resource type, set at creation and cannot be changed. After you create an automation, you add triggers to it from its detail page.

## Automation types

Operations Manager supports four automation types:

| Type                  | Resource                                   |
| --------------------- | ------------------------------------------ |
| **Workflow**          | A workflow in Studio                       |
| **Agent**             | An agent in Agent Builder                  |
| **Compliance Report** | A compliance plan in Configuration Manager |
| **Lifecycle**         | A Lifecycle Manager resource model         |

The automation types you see depend on the products and applications installed in your environment, so you might not see every type listed here.

For type-specific behavior, see the following:

* [Agents](/itential-platform/operations-manager/agents)
* [Compliance reports](/itential-platform/operations-manager/compliance-reports)
* [Lifecycle Manager actions](/itential-platform/operations-manager/lifecycle-manager-actions)

## Create an automation

#### Open the Create Automation dialog

Click the **(+)** icon button in the top-left toolbar of Operations Manager. The **Create Automation** dialog appears.

#### Select the automation type

Select an automation type and click **Create**. After creation, you cannot change the automation type.

#### Select a resource

Select the resource to associate with the automation. The resource field reflects the automation type — for example, a **Workflow** dropdown for workflow automations, or an **Agent** dropdown for agent automations. Only resources you have permission to access are shown.

#### Configure access

Add the user groups that should have read or write access to this automation. For more information, see [Access control](#access-control) and [Authorization](/itential-platform/admin-essentials/authorization).

#### Save

Click **Save Changes**. You can then add triggers to the automation from its detail page.

## Access control

Access to an automation is set at the automation level using user groups configured in Admin Essentials.

| Access level | What it allows                                                                |
| ------------ | ----------------------------------------------------------------------------- |
| **Read**     | Execute enabled triggers and view sessions or jobs launched by the automation |
| **Write**    | Update the automation configuration and its triggers                          |

## Add triggers

After saving an automation, add triggers to it from the automation's detail page. Triggers define when and how the automation runs.

For information about trigger types and configuration, see [Triggers](/itential-platform/operations-manager/triggers#trigger-types).