The Agent Node enables the use of AI‑powered, goal‑driven agents within Xponent workflows. It allows agents to be executed as part of graph orchestration, where they can apply goals, knowledge sources, and available tools to perform decisions or actions within a journey. By using Agent Nodes, teams can reduce manual or repetitive workflow logic and introduce intelligent decision support directly into graphs.
Prerequisite
Xponent Intelligence: An administrator must enable Xponent Intelligence at the organization level. Also, in the Xponent Intelligence settings, the Agent Node toggle must be enabled for you to create agents.
When the Agent Node feature is turned off at the organization level, you can view existing agents but cannot create new ones. Any Agent Nodes already used in workflows continue to run without interruption.
.png?sv=2026-02-06&spr=https&st=2026-07-22T10%3A05%3A47Z&se=2026-07-22T10%3A19%3A47Z&sr=c&sp=r&sig=0SvO7HbMDiOR77c7Hhj%2BcUaRLAMySuIbx%2FXjqSeRoC4%3D)
When the Agent Node feature is turned on but no AI Agents exist in the organization, the Agent page displays an empty state to guide you in creating your first agent.
The empty state provides a brief explanation of the agent’s purpose and highlights how they can be used in Xponent workflows. A Create Agent button is prominently displayed to start the agent creation process.
Until at least one agent is created, the agent list table, filters, and related actions remain hidden.
.png?sv=2026-02-06&spr=https&st=2026-07-22T10%3A05%3A47Z&se=2026-07-22T10%3A19%3A47Z&sr=c&sp=r&sig=0SvO7HbMDiOR77c7Hhj%2BcUaRLAMySuIbx%2FXjqSeRoC4%3D)
Sorting, Filtering, and Searching
The Agents page displays all AI Agents available at the organization level, allowing you to review their configuration, readiness, and access to Xponent Graphs before creating or managing agents.
Sorting
When one or more agents exist, the page displays a searchable and sortable list of agents. Each column provides key information at a glance, including:
Agent Name: The name assigned to the agent during creation. This helps identify the agent’s purpose within the organization.
Agent ID: A system‑generated, unique identifier for the agent. The Agent ID is used for internal reference and troubleshooting.
Goal and Context: A brief summary of the agent’s defined goal and contextual information. If the text is longer than the column width, it is truncated. Hover over the Read more text to view the complete goal and context.
Graph Environment: Indicates if the agent has access to Xponent Graphs and identifies the single environment it is configured for. For Example, Production, Pre‑Production, or Non‑Production
Date Created: The date on which the agent was created. By default, agents are sorted by this column in descending order (newest first).
Status / Readiness: Reflects the agent’s operational state based on internal readiness checks and indicates whether the agent is available for use in workflows. For Example,
🟢 Ready or⚫ Not ReadyAction: Provides an option to view the agent’s details, allowing you to review the full configuration, including goals, knowledge sources, tools, and status.
You can sort the list by Agent Name, Date Created, or Graph Environment by selecting the column headers in ascending or descending order.
.gif?sv=2026-02-06&spr=https&st=2026-07-22T10%3A05%3A47Z&se=2026-07-22T10%3A19%3A47Z&sr=c&sp=r&sig=0SvO7HbMDiOR77c7Hhj%2BcUaRLAMySuIbx%2FXjqSeRoC4%3D)
Filtering
The agent list provides quick filtering and search options to help you find agents easily. Two status filter buttons are available at the top of the agent list:
🟢 Ready: Shows agents that are operational and available for use in workflows.
⚫ Not Ready: Shows agents that are not yet ready for use.
These buttons display the count of agents matching that status. Selecting a filter updates the agent list immediately. Selecting the same filter again (double‑selecting) clears the filter and returns the list to its default state.
Searching
The agent list includes a search field that lets you search for agents by Agent Name, Agent ID, Goal, or Context. Once you enter this metadata, the list updates to show matching agents.
If no agents match the entered text, the following message is displayed: “No results found for “<entered text>”. Check for typos or try different keywords. You can also create a new agent if none match what you're looking for.”
This helps you refine their search or quickly create a new agent when needed.
.gif?sv=2026-02-06&spr=https&st=2026-07-22T10%3A05%3A47Z&se=2026-07-22T10%3A19%3A47Z&sr=c&sp=r&sig=0SvO7HbMDiOR77c7Hhj%2BcUaRLAMySuIbx%2FXjqSeRoC4%3D)
Status filters, search, and column sorting can be used together to narrow down large agent lists and quickly find the required agents.
Viewing Agent Configuration
You can view the configuration details of an existing agent directly from the Agents list.
In the Action column of the Agents list, select the View (eye) icon for the required agent.
The agent configuration opens in view‑only mode.
In view mode, the following sections are displayed for reference:
Basic Setup: Displays the agent’s name, goal, and context, guardrails, and selected base model.
Knowledge: Shows the knowledge configuration for the agent, including goal and context for the knowledge and any uploaded or processed knowledge files.
Tools: Displays the tools configured for the agent, such as Xponent Graphs, API tools, or generic tools (for example, Web Search).
The agent configuration is read‑only and cannot be modified from the view screen.
.gif?sv=2026-02-06&spr=https&st=2026-07-22T10%3A05%3A47Z&se=2026-07-22T10%3A19%3A47Z&sr=c&sp=r&sig=0SvO7HbMDiOR77c7Hhj%2BcUaRLAMySuIbx%2FXjqSeRoC4%3D)
Best Practices for Creating Agents
Give each agent a focused responsibility. Agents with a single, well‑defined goal are easier to understand, test, and reuse across multiple graphs.
Include only the information the agent needs to perform its task effectively. Excessive or unrelated context can reduce clarity and impact decision‑making.
Avoid creating multiple agents with overlapping goals. Reusing agents helps maintain consistency and reduces configuration overhead at the organization level.
Grant agents access only to the tools and Xponent Graphs required for their purpose. This helps minimize unintended behavior and simplifies troubleshooting.
Assign clear names and meaningful goal descriptions so other users can easily understand what the agent is designed to do.
Begin with a basic configuration and expand the agent’s knowledge or tools as requirements evolve. This makes testing and validation easier.