Use agent triggers

FlowAI

In Operations Manager, you create automations that run an agent on a trigger. You can use any trigger type for an agent automation: manual, schedule, or API.

Agent Projects is where you create and configure agents. After your agent is ready, create an automation in Operations Manager to bind it to triggers and control who can run it.

Before you begin

Before you begin, make sure that you have the following:

  • An active FlowAI subscription, which is an add-on to Itential Platform. To subscribe, contact your Customer Service Manager (CSM).
  • One or more agents configured in an agent project. For information, see Agents.

Create an agent automation

Follow the steps to create an automation and select Agent as the automation type. The following steps are specific to agent automations.

1

Select an agent

Choose the agent from the Agent dropdown. Only agents you have permission to access are shown. You must be a project Owner or Editor for the agent’s project, or have been granted operator access on the individual agent by a builder. For information about permissions, see Agent project permissions.

2

Configure access

Add the user groups that should have read or write access to this automation. Users with read access can run enabled triggers and view the sessions launched by this automation in Agent Sessions. Users with write access can also update the automation configuration and its triggers. For more information, see Authorization.

Run a manual trigger

When you manually run an agent trigger, a new browser tab opens to the session detail in Agent Sessions.

If the session fails to start, no tab opens and an error message is shown in Operations Manager. Common causes:

CauseWhat to do
No gateway cluster configured in the model registryContact your LLM Admin to configure a gateway cluster in Admin Essentials.

Edit and delete

For information about filtering, editing, and deleting automations and their triggers, see Triggers.

If you delete an agent from Agent Projects, automations that referenced it show a broken reference error. Past session history remains visible in Agent Sessions.