UiPath Integration Service: the agent-ready connectivity layer for enterprise automation and AI

Your AI agents are only as useful as the systems they can reach

UiPath Integration Service has evolved into the agent-ready connectivity layer for enterprise automation and AI—giving agents, robots, workflows, and applications a governed path to the systems where work actually happens. Coding agents build the integrations. Integration Service gives teams a governed way to manage the credentials, actions, and events behind them.

The missing link between intelligence and action

For many enterprises, automation and AI deliver only as much value as the systems they can reach—so connectivity is what unlocks their full value.

You can buy the smartest agent on the market, but it cannot do real work until it can read a record from Workday, write a ticket into ServiceNow, post a message in Slack, kick off a flow in SAP®, and react to a webhook from Salesforce—all without leaking credentials, breaking on a token refresh, or stalling out the moment a system lives behind a firewall.

That’s what UiPath Integration Service solves. It connects the UiPath Platform™ to enterprise systems, applications, APIs, and event sources, and it gives agents, robots, workflows, and apps a single, governed way to act.

What began as a connector layer is becoming something bigger: a common integration layer for building, running, and governing agentic automation across the enterprise.

Why now? Coding agents are changing integration.

Until recently, teams typically relied on one of two primary paths for integrating systems into automation. You either picked from a catalog of prebuilt connectors, or you wrote and maintained the integration yourself—authentication, payloads, mappings, error handling, the works. Both paths had limits. Connector catalogs cannot keep pace with every SaaS app and long-tail system. Hand-coded integrations slow delivery and become someone’s part-time job to maintain.

Coding agents change the dynamic. With UiPath CLI and Integration Service skills, a coding agent can generate and configure much of an integration far faster than a developer starting from scratch. But that creates a new problem: agents can build integrations faster than any team can govern them. Without a shared control layer, credentials can sprawl, connections can multiply, and audit records can become fragmented.

Imagine you want an agent to assign each new sales lead to the right representative. To make that decision, it may need to retrieve the lead from Salesforce, check representative capacity in a workforce system, look up territory rules in a database, and access an internal application that has never been exposed to the public internet.

Each system has its own authentication model, data structure, and operational quirks. The agent needs a secure and reliable way to work across all of them, while credentials remain protected in your enterprise vault rather than embedded in code or configuration files.

A coding agent can generate the steps and connector activities the workflow needs. Integration Service provides the approved connections, manages the credentials, applies access policies, and reaches private systems through Relay when required.

Previously, this was days spent on auth, payloads, and error handling. Now, your coding agent can build most of it—if you give it a connectivity foundation that’s governed by default.

That’s what Integration Service is now built to be.

What you get: connected systems, governed access, agent-ready integrations

UiPath Integration Service brings together everything teams need to build integrations—with coding agents, pre-built connectors, Connector Builder, and HTTP activities—run them under enterprise governance, respond to business events with triggers, reach systems behind the firewall with Relay, and extend workflows through MCP. Each is useful on its own. Together, they help teams build integrations faster without creating a new sprawl problem underneath them.

Build integrations the way your team works

Teams use the coding agent of their choice to build and configure integrations end to end. Connectors are exposed as integration skills the coding agent uses through the UiPath CLI, so the agent already knows how to authenticate to Salesforce, what shape a ServiceNow ticket needs, and which actions are available on Workday. For systems without a prebuilt connector, the coding agent works from API documentation or OpenAPI/Swagger specs to generate HTTP activities on the fly—or the team can build a reusable connector using Connector Builder.

Coding agents are the primary path, but they're not the only one. Prebuilt connectors, reusable connections, guided setup, and Connector Builder remain available for teams who prefer a visual or low-code experience. The same building blocks—activities, triggers, and connections—work either way .

Run them through shared enterprise connections

Every integration on Integration Service runs on the same shared plumbing: reusable connections, credential vaulting with CyberArk, HashiCorp Vault, and others, folder-aligned access control, centralized role-based access control (RBAC), and audit trails for every connection, credential access, and trigger activation. The same controls govern humans, workflows, and agents—because in an agentic world, you cannot have one policy for people and another for the agents acting on their behalf.

Because the coding agent works through Integration Service, integrations it builds inherit that governance automatically: credentials stay out of generated code, approved policies determine what the agent can use, and a connector disabled by an Automation Ops policy simply isn't available to the agent.

Respond to business events

Workflows and agents can be triggered two ways. Real-time webhooks fire the moment a business event happens—an opportunity closes in your client relationship management (CRM), a ticket changes state in your information technology service management (ITSM), a record drops into a shared folder. Reliable pollers cover the systems that don't emit events, with frequencies as low as one minute.

Reach cloud and private-network systems

Not every system lives in the cloud. With Relay, Integration Service reaches on-premises and private-network systems over a secure, outbound-only connection—no VPN, no inbound firewall ports to open—so the same governed connectors work whether a system runs in the cloud or in your data center. Read more about Relay.

Extend workflows through MCP

The Integration Service MCP connector, currently in preview, lets a UiPath workflow use tools exposed by compatible MCP servers directly as workflow activities—instead of creating a separate custom activity or adapter for each server. It's how workflows tap into the growing MCP ecosystem without leaving the platform's governance model.

Bring your data tier into the agentic enterprise

Relational databases are still where the most important enterprise data lives, and they are also where many automation projects stall. The Database Hub connector brings the same agent-ready, governed connectivity model to the data tier.

It’s a JDBC-based connector that works across the databases enterprises actually run—SQL Server, PostgreSQL, Oracle, Redshift, and Databricks—with enterprise-grade authentication tailored to each engine. Trigger workflows automatically on row insertions or updates, and interact with databases using built-in CRUD activities or custom SQL for SELECT queries. And because it’s an Integration Service connector, every query runs under the same RBAC, vaulting, and audit controls as any other connection.

The Database Hub connector is available today in public preview for cloud-reachable databases.

Built for the agentic enterprise

Integration Service is built for a world where automation isn’t just people clicking buttons or robots running scripts—it’s a mix of agents, robots, workflows, and applications all acting on enterprise systems at once. That changes what an integration layer needs to be.

It needs to be agent-driven by default, so coverage doesn’t bottleneck on a connector roadmap. It needs to be governed by default, so credentials don’t scatter as automation actors multiply. And it needs to be consistent across every actor, so the same vaulted credentials, audit trail, and access controls apply whether the call comes from a person, a workflow, or an agent.

The goal is not to let coding agents create unmanaged point-to-point integrations faster. It is to separate integration creation from connection governance. Builders can move faster, while platform teams retain control over credentials, policies, network access, and auditing.

That’s what Integration Service delivers. Faster integration delivery. Broader system coverage. Less manual work. And a foundation you can scale across the enterprise without giving up control.

Get started

The stronger the connectivity layer, the further automation can go. Integration Service brings the connectivity your automation needs, at the speed your team wants to move, under the governance your enterprise requires—the foundation for agents and workflows that act reliably across the systems your business runs on.

Explore Integration Service to see it in action. Ready to talk through your use case? Get in touch.

Editor's note: this blog post was coauthored by Robert Baron, Senior Product Marketing Manager at UiPath.