Skip to main content

Agents

An Agent is what the user actually talks to in the Chat. Every Agent lives inside exactly one AI Space.

Agents list page​

Standard table — agents, edit button per row, Create button.

Create / edit an agent​

FieldPurpose
Display NameHuman-friendly name shown in the UI.
Agent IDLowercase only. Must match exactly the agentName value of the Agent Node inside the Start Flow you specify below. Mismatch → "Invalid agent data!" when the user talks to the agent from the Chat.
Start FlowThe flow file the engine runs when the agent receives a prompt (e.g. pdf.flow.js).
Start NodeThe label of the entry node within that file (e.g. Start).
SpacePick the AI Space that owns this agent.

How Start Flow + Start Node tie back to the code​

The mental model is similar to Salesforce Commerce Cloud (SFCC) XML Pipelines.

Every agent must have a Start Node and an End Node in its flow. The Start Flow field is a pointer to the file where that Start Node lives.

When a user prompts an agent in the Chat:

  1. The system knows the Space (because the Consumer is assigned to it).
  2. The system knows the Agent (because the user is talking to it).
  3. The agent's /org configuration tells the engine which Start Flow file and which Start Node label to enter.
  4. The engine resolves the file in the Space's folder and starts execution there.

If any of Agent ID (in /org) ↔ agentName (in Agent Node) ↔ Start Flow (file name) ↔ file on disk are out of sync, the runtime can't find the entry.

Constraint to remember​

  • An Agent belongs to exactly one Space. If you need the same logic in multiple Spaces, duplicate the agent (or refactor shared logic into a sub-flow callable via Run Flow).
  • A Space, by contrast, can hold many Agents.
  • AI Spaces — the Space owns the Agent.
  • Agent Node — the in-flow node whose agentName must match this Agent's ID.
  • Start Node — the entry-node concept that the Start Node field here points at.