Concepts and terminology
Use this page to connect the names you see in the product, the documentation, and MCP tools.
Hyperflow / Hyper Flow
Automation logic composed of actions and data. The navigation label is Hyper Flows.
An AI conversation.
Autom
A name still used in existing automation records, APIs, and MCP tools.
A separate promise that every business outcome succeeded.
Action
A step that interacts with a system, transforms data, or controls execution.
An entire reusable service.
Application / app
An integration area containing capabilities for a connected system.
A credential authorizing that connection.
Application credential
Connection configuration used for an external application.
Agent instructions or a service input.
Work Item
Govern, Execute, or Prove work used by a service, with a released version selected for use.
An entire Service Case.
Service
A reusable outcome contract and the lifecycle used to deliver and verify it.
One customer's individual request.
Deployment
A service's target configuration, including the tenant and required bindings.
Proof that the service has run.
Service Case
The operational record followed through the service lifecycle.
An Autom run identifier returned by MCP history.
AI Agent
An assistant configured inside AI Agent Composer with model, instructions, knowledge, skills, and channels.
A Mate Agent/runtime.
Mate Agent
The execution component managed under Manage → Mate Agents.
A conversational AI Agent.
MCP
The connection through which a compatible external AI client discovers and calls exposed tools.
A guarantee that every product feature has a tool.
Two connected paths
The diagram connects product concepts. MCP clients can use the operations listed in the MCP tool reference; a product capability is not automatically an exposed MCP tool.
Three meanings of success
A request was accepted: the platform received or started work.
Execution completed: the runtime reports a terminal execution state.
The intended result was verified: output or destination evidence establishes the business result.
Keep these separate in dashboards, support conversations, and AI-generated answers. Service Case status and result and MCP run states use different vocabularies.
Last updated
Was this helpful?

