Skip to content

Agentic Flow in XTM One

Agentic Flow covers two related views in XTM One:

  • the global handover graph opened from the main sidebar
  • the detail page of a specific saved flow

Both views help you understand how agents cooperate.

What Agentic Flow is for

Use these views when you want to:

  • understand how one agent hands work to another
  • see the structure behind a shared workflow
  • inspect the path a task can follow
  • review or adjust that structure, if you are allowed to edit it

Understand the handover types

The graph uses named connection types between agents.

  • Delegate sends work to another agent in the background.
  • Consult asks another agent for help and returns to the original agent.
  • Transfer moves the conversation to another agent.
  • Mandatory transfer forces the conversation to continue with another agent.

These labels matter because they change how the user experience behaves in chat and in automation.

The global Agentic Flow page

Choose Agentic Flow from the left sidebar to open the platform-wide graph.

This page shows:

  • all visible agents in one graph
  • the handover links between them
  • a warning that changes affect global behavior
  • a focus field so you can isolate one or more agents
  • a graph you can pan and zoom

Use the focus field

Large graphs are easier to read when you focus on a few agents.

Use the focus field to:

  • highlight one agent
  • compare a few related agents
  • reduce visual noise in a large environment

You can add and remove focused agents directly from the filter area.

Open an agent from the graph

You can open an agent directly from the global graph.

This is useful when you want to move from a visual connection view to the full agent detail page.

Editing the global graph

If your role allows it, the global graph is not only a viewer. It can also be an editing surface.

Authorized users may be able to:

  • create a new handover between two agents
  • change the type of an existing handover
  • remove a handover

Because these are global relationships, a change here affects all users who rely on that agent behavior.

The flow detail page

A saved flow has its own detail page. This page is more structured than the global graph and focuses on one defined workflow.

The standard tabs are:

  • Overview
  • Config
  • Memory
  • Flow
  • Activity

Overview tab

Use Overview to understand the flow at a glance.

This tab can show:

  • the agents included in the flow
  • whether they are active
  • summary statistics
  • warnings about broken or incomplete handovers
  • add and remove actions for flow membership

If you manage the flow, this is often the quickest place to adjust which agents belong to it.

Config tab

Use Config for the flow’s own identity and shared settings.

Depending on your permissions, this can include:

  • the flow name and description
  • the icon
  • the entry agent
  • visibility and sharing settings

Memory tab

Some flows use shared memory.

When that is enabled, the Memory tab lets authorized users:

  • search flow-level memory
  • review memory health
  • maintain or optimize stored entries
  • edit or remove stored entries

This memory is shared at the flow level rather than being tied to only one agent.

Flow tab

The Flow tab is the graph view for the saved flow itself.

It helps you:

  • see only the agents in that flow
  • understand the handovers inside that flow
  • review warnings in a smaller, more focused graph

This is often the easiest graph view for day-to-day operational understanding.

Activity tab

The Activity tab aggregates runs across the agents in that flow.

Use it to:

  • review recent work from the whole flow
  • understand whether the workflow is active
  • open related runs without checking each agent one by one

Header actions on a flow

A saved flow can also have actions in the page header.

Depending on permissions, you may be able to:

  • chat with the flow
  • export the flow
  • delete the flow

What the entry agent means

If a flow has an entry agent, that agent becomes the chat entry point for the flow.

If no entry agent is configured, the flow may still exist and run, but chat from the flow header is not available.

Deleting a flow

When a flow is deleted, XTM One can also offer the option to delete the agents inside that flow.

That is an important decision:

  • deleting only the flow removes the grouping
  • deleting the flow and its agents removes the assistants, assignments, runs, and related memory as well

Read-only and shared flows

As with agents, some flows are visible but not editable.

You may see:

  • a company-managed badge
  • a shared badge
  • a read-only state

That means you can inspect the flow, but only certain users can change it.

Next step

The next chapter explains Work History, where you review runs, waiting items, notifications, and execution details.