Salesforce vs UiPath (2026)

Agents act on the customer's systems through actions. Agentforce Builder connects agents to data, channels and existing Salesforce assets including Flows, Apex, MuleSoft APIs and prompt templates, and out of the box actions cover common jobs such as order and reservation management.

Sourcesalesforce.com/agentforce/agent-builderread 2026-09-18

Tools connect an agent's reasoning to real actions, giving it access to data in business applications and the ability to execute functions, and an agent can only act through tools it has been explicitly granted, described in the system prompt with when to use them. Integration Service adds an MCP Connector that lets workflows call tools from any compatible MCP server as a native activity, Database Hub to read and write systems such as SQL Server, Oracle and Databricks without custom code, and Relay to reach on premises systems from cloud automations.

Sourcedocs.uipath.com/agents (agent tools) and uipath.com/newsroom/uipath-platform-updates-fusionread 2026-10-24

Agent Script defines how work moves through an agent. Every request begins at an agent router that sets initial variables and classifies the request, then the agent processes a subagent and transitions between subagents along paths the script defines. Across agents, an orchestrator agent can invoke specialized agents in other Salesforce orgs and outside Salesforce through the Agent API, and a flow action can invoke an agent as one step of a longer automation.

Sourcedeveloper.salesforce.com/docs/ai/agentforce/guide/ascript-flow.mdread 2026-09-18

UiPath orchestrates agents of every origin, UiPath system agents, low-code agents, coded agents and external agents, inside one platform, where agents work alongside activities, other agents, apps, human tasks and Maestro for business process orchestration, and are managed, scheduled and monitored through Orchestrator.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide/agent-capabilities-in-the-uipath-platform.mdread 2026-09-18

Headless agents are called without a human trigger from a user interface. An Apex trigger or a scheduled job calls the agent as part of a background process, and a standard AI Agent action lets any flow, including one started by a record change, invoke an active agent with a prompt.

Sourcedeveloper.salesforce.com/blogs/2025/04/build-headless-agents-with-the-agent-api.htmlread 2026-09-18

Agents deploy as processes in Orchestrator, which schedules and launches jobs through time triggers at regular intervals and queue triggers that start the automation whenever new items are added to a queue, so agents run without anyone asking.

Sourcedocs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-triggers.mdread 2026-09-18

Agents are grounded in the customer's own material. An Agentforce Data Library connects an agent to trusted unstructured or semi structured sources, such as files or a knowledge base, which the customer adds to the library and the agent retrieves from when it answers, and new material is added to the library with no retraining.

Sourcedeveloper.salesforce.com/docs/ai/agentforce/guide/headless-examples-agent-adl.mdread 2026-09-18

An index added as agent context gives the agent access to a permissioned knowledge base of the customer's own content, and the builder configures the search strategy and scope that decide what the agent retrieves.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide/agent-contexts.mdread 2026-09-18

Agent Script variables carry context through a session, shared by every subagent, and a session ID carries it across invocations.

Beyond the session, Data 360's Agentic Memory extracts a summary of each conversation, profile facts and preferences from a registered agent's conversations. Memory is scoped to a data space and a unified individual, and agent level access control decides which agents read which memories. Conversation summaries and profile facts persist until deleted, while preferences fade unless they are reinforced, and an expired entry can be recovered by updating its validTo field.

Memory Management APIs create, retrieve, update and delete memory entries, which is how a product lets people view, edit and delete their own facts and preferences. Deletion is permanent.

Sourcedeveloper.salesforce.com/docs/data/agentic-memory-context memory overview and memory managementread 2026-10-25

Agent memory, in preview, keeps memory spaces that several agents can share. Episodic memory holds the inputs, outputs and outcomes of past cases with the feedback attached to them, and items enter it when a person promotes feedback from an agent run. Escalation memory stores how a person resolved an escalation in Action Center.

Before each run a recall step embeds the current inputs, finds similar items and adds them to the agent's context as examples, and before raising an escalation the agent checks for a matching resolution. Memory items can be inspected, edited and deleted from the Memory spaces tab. Nothing is written to memory by the agent on its own, and no retention period or expiry is stated.

Sourcedocs.uipath.com agents user guide, agent memoryread 2026-10-25

Escalation to a person is a built in agent utility. The utils.escalate call hands the conversation to a human service rep through an Omni-Channel routing connection the customer defines, and instructions tell the agent when to call it. Agent Script structures what the agent may do, with every request passing an agent router that classifies it before any subagent runs and explicit transitions between subagents, and Salesforce's own guidance recommends a person check model responses before they are shared in most use cases.

Sourcedeveloper.salesforce.com/docs/ai/agentforce/guide/ascript-ref-utils.mdread 2026-09-18

Escalations, powered by Action apps in Action Center, let a developer have the agent validate business details with a person before running a tool, request approval, or ask for manual assistance on a business exception. Each escalation carries a prompt that tells the agent when to raise it, and is routed to a specific user, to the least-loaded member of a group, to all group members, or round robin. Runtime Checker validates agent behavior against defined policies while the agent is running, not only when it was built, and an LLM as judge guardrail evaluates outputs against custom criteria.

Sourcedocs.uipath.com/agents (agent escalations) and uipath.com/newsroom/uipath-platform-updates-fusionread 2026-10-24

Salesforce holds attestations scoped to the agent layer itself, including a SOC 2 report and a SOC 3 report for the Einstein Platform and Agentforce on Hyperforce, an ISO 42001 certificate covering the Salesforce AI Platform and Agentforce, a PCI attestation of compliance for Data Cloud, the Einstein Platform and Agentforce, a C5 report, an IRAP assessment and Spain ENS High for the Einstein Platform and Agentforce, alongside FedRAMP High and Moderate and ISO 27001 categories.

Sourcecompliance.salesforce.com/enread 2026-09-18

UiPath's trust portal publishes a SOC 2 Type 2 report, an ISO 27001 certificate, a HITRUST certificate, C5, IRAP, HIPAA and Spain's ENS certificate of conformity. The customer-facing controls on the agent layer are Automation Ops policies applied through the AI Trust Layer at tenant level, which control whether users can access and use agents across the organization.

Sourcetrust.uipath.comread 2026-09-18

Every step of an agent interaction is recorded. The Agentforce Session Tracing data model and the Generative AI Audit and Feedback data model capture turns, messages, LLM calls, actions, metric scores and feedback, and the Session Trace OTel API exports a full session as OpenTelemetry JSON for any observability tool or OTLP collector. Trace files can also be managed from the command line during development, and the Einstein Trust Layer keeps an audit trail of generations.

Sourcedeveloper.salesforce.com/docs/ai/agentforce/guide/otel-api.mdread 2026-09-18

Every agent run leaves a trace, a detailed record of the steps taken, data processed, decisions made and results generated, with timestamps, errors, inputs and outputs, so a failed tool call can be inspected at the exact step with its inputs, outputs and error. UiPath positions traces for debugging, performance analysis of latency, errors and throughput, and compliance and auditing as a verifiable record of what the agent did, when and how.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide/agent-traces.mdread 2026-09-18

Salesforce runs on Hyperforce, its public cloud infrastructure, where customer data is generally stored in the country where the customer's org is located, provided the services in use are available in that Hyperforce country, and a secure backup of an org can be held in a secondary Hyperforce region.

Sourcesalesforce.com/platform/public-cloud-infrastructureread 2026-09-18

UiPath comes in two delivery models, Automation Cloud, its cloud service, and Automation Suite, which runs the platform on the customer's own premises, each with its own documentation set. Automation Suite now runs on Linux with the full agentic AI stack, so agents, robots and people work inside infrastructure the enterprise already operates.

Sourcedocs.uipath.com/llms.txt and uipath.com/newsroom/uipath-platform-updates-fusionread 2026-10-24

Agentforce Builder starts agents from out of the box subagents, actions and templates that cover common jobs such as order management, reservation management and general FAQs, which the customer then extends and refines with natural language instructions.

Sourcesalesforce.com/agentforce/agent-builderread 2026-09-18

UiPath ships agent templates, available on the Agents page in Automation Cloud and in UiPath Marketplace, each preconfigured for a specific task with a system prompt, activity tools with descriptions and starter evaluation sets, needing only minimum configuration to run and open to modification.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide/using-agent-templates.mdread 2026-09-18

An administrator sets the org level model for Agentforce on the Agentforce Agents page in Setup, and Agent Script overrides it for a specific agent or subagent with a model configuration naming any supported model. The supported list spans Salesforce managed models from OpenAI, Anthropic on Amazon Bedrock, Google Gemini on Vertex AI and Amazon Nova, most running inside the Salesforce trust boundary, and customers can also bring their own model.

Sourcedeveloper.salesforce.com/docs/ai/agentforce/guide/ascript-model.mdread 2026-09-18

The builder chooses the model for each agent at design time and refines that choice once evaluations show how different models perform on accuracy, stability, speed and cost, and a custom model can be configured for Context Grounding through the admin guide's LLM configuration.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide/choosing-the-best-model-for-your-agent.mdread 2026-09-18

The Agent API opens a conversation with an agent, sends prompts synchronously or as a stream of server sent events marking progress, text chunks and the end of each turn, and closes the session, authenticated through a connected app with OAuth scopes, with a public Postman collection and Node.js client. Inside the platform, an invocable action runs any active agent from Apex or Flow, and Salesforce Hosted MCP Servers expose Salesforce data and automation to external AI agents and LLM applications over MCP.

Sourcedeveloper.salesforce.com/blogs/2025/04/build-headless-agents-with-the-agent-api.htmlread 2026-09-18

With a UiPath SDK, developers build coded agents in their own IDE, package them and deploy them to Orchestrator as standard packages, where they run as processes under the same governance as other automations, and they can connect the project to Studio Web for debugging, evaluation and publishing.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide/about-coded-agents.mdread 2026-09-18

Agents are tested before release with scored test cases. A test spec sets out test cases as utterances with the expected agent behavior, can set context variables and include ready made metrics in the output, and is created and run in a development org from the command line or the Agentforce Testing Center, with pass and fail results.

Sourcedeveloper.salesforce.com/docs/ai/agentforce/guide/agent-dx-test.mdread 2026-09-18

Evaluations check agents against defined cases before and during release. An evaluation pairs an input with an evaluator that checks the agent's output or trajectory against the expected result, evaluation sets group evaluations, and each run produces a score from 0 to 100 with traces of the evaluation runs to diagnose failures and re-run. Evaluations can be created from correct past runs, and evaluation results guide model choice.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide/agent-evaluations.mdread 2026-09-18

Operating a browser or desktop interface is not part of Agentforce. Agents act through actions, flows, Apex, APIs, prompt templates and MCP tools, reached through the agent router and subagents in Agent Script.

Sourcedeveloper.salesforce.com/docs/llms-genai.txtread 2026-09-18

Robots operate real application interfaces in attended and unattended automation, and Healing Agent autonomously detects and recovers from UI automation failures caused by changing interfaces, network throughput and evolving UI frameworks, using just-in-time analysis of the automation to choose a recovery strategy.

Sourcedocs.uipath.com/agents/automation-cloud/latest/user-guide-ha/what-is-healing-agent.mdread 2026-09-18