Connect UiPath to enterprise systems, applications, APIs, and event sources. Build integrations with your coding agent of choice or configure them visually.
Connect UiPath to enterprise systems, applications, APIs, and event sources. Build integrations with your coding agent of choice or configure them visually.
The connectivity layer between UiPath and your enterprise systems. Coding agents assemble integrations from three reusable building blocks: activities, triggers, and connections. UiPath governs credentials, actions, and events across agents, robots, workflows, and apps.
When integration stops being a bottleneck, automation moves at the speed of the business it runs.
Teams using a coding agent of choice cut the time needed to build and configure integrations.
Less hand-coded authentication, payload construction, API handling, and maintenance overhead.
Event-driven triggers let automations and agents act the moment business events happen.
One governed integration layer with centralized credentials, lifecycle controls, folder alignment, and audit visibility.
Build with your coding agent of choice or configure them visually with pre-built connectors. All on one governed control plane.
CODING AGENTS
Point your coding agent of choice at a system and it builds the integration end to end, configuring activities, triggers, and connections. It works from a pre-built connector where one exists, or from API documentation, OpenAPI, or Swagger where it doesn’t.
VISUAL CONFIGURATION
Prefer a guided, hands-on approach. Configure the same activities, triggers, and connections visually. Integration Service comes with a catalog of pre-built connectors, and Connector Builder for custom integrations.
However a system exposes itself, there’s a path to connect it, starting with your coding agent of choice.
Coding agent generates connectivity for systems with no pre-built connector, from API documentation, OpenAPI, or Swagger.
Pre-built connectors for systems of records, databases, external agents, and legacy systems; Connector Builder for reusable custom connectors.
HTTP to go beyond pre-built connectors, and webhook for real-time events; Relay reaches private and on-premises systems from the cloud.
For systems with no API, UI automation reaches them through their interface.
Reusable connections: configure once and share them across activities, triggers, and workflows.
Workflows and agents fire from real-time system events, webhooks, and notifications. Triggers are governed alongside the connections they depend on, with the same RBAC and audit trail.
Pre-built event listeners for supported enterprise systems.
Webhook connector receives real-time events from any system.
Trigger activations captured in the platform audit history.
Integration Service plugs into MCP, so your workflows can tap a growing set of third-party tools.
Consume third-party MCP servers directly inside your workflows.
Governed on the same control plane as your connections.
However a system exposes itself, there’s a path to connect it, starting with your coding agent of choice.
Coding agent generates connectivity for systems with no pre-built connector, from API documentation, OpenAPI, or Swagger.
Pre-built connectors for systems of records, databases, external agents, and legacy systems; Connector Builder for reusable custom connectors.
HTTP to go beyond pre-built connectors, and webhook for real-time events; Relay reaches private and on-premises systems from the cloud.
For systems with no API, UI automation reaches them through their interface.
Reusable connections: configure once and share them across activities, triggers, and workflows.
Workflows and agents fire from real-time system events, webhooks, and notifications. Triggers are governed alongside the connections they depend on, with the same RBAC and audit trail.
Pre-built event listeners for supported enterprise systems.
Webhook connector receives real-time events from any system.
Trigger activations captured in the platform audit history.
Integration Service plugs into MCP, so your workflows can tap a growing set of third-party tools.
Consume third-party MCP servers directly inside your workflows.
Governed on the same control plane as your connections.
Governance is built into Integration Service. The same credential vault, access controls, and audit trail apply across the agents, robots, workflows, and apps that use a connection.
Connections are protected by fine-grained RBAC, so the right actors use the right connections.
Credentials sit in a centralized vault, not hand-coded into workflows or exposed to the actors that use them.
Reusable connections are scoped to UiPath folders, aligning connection access to your platform structure.
Credential access, connection use, and trigger activations are captured in a full audit trail.
Connector health, token refresh, and deprecation are managed across the connector lifecycle.
Every pattern below uses the same connector infrastructure: governed credentials, reusable connections, and consistent authentication across agents, robots, workflows, and apps.
WORKFLOW APPS
Build apps and workflows that read and write live data across CRM, ERP, ITSM, HR, and collaboration systems through governed, reusable connections.
EVENT-DRIVEN
Use application events, webhooks, API events, and system notifications to launch workflows the moment something changes in an external system.
AGENT-DRIVEN ACTIONS
Give your agent a governed way to retrieve data and take action across enterprise systems through pre-built connectors, OpenAPI or Swagger specs.
BROCHURE
An overview of the connectivity layer, the activities + triggers + connections architecture, and the capabilities your teams use to deliver enterprise integrations.
"Using the UiPath OpenAI Connector, we can leverage GPT models to prewrite responses to customer inquiries, or for summarizing and distilling longer documents into key points. This is an asset when faced with character limits or size constraints."
Activities, triggers, connections, governance, and the full reference.
Individual connector pages for supported systems across SaaS, databases, and apps.
Build and publish custom integrations when no pre-built connector fits the system you need.
Hands-on courses for Integration Service, connector building, and event-driven automation patterns.
UiPath Integration Service is the agent-ready connectivity layer for enterprise automation and AI. It connects UiPath to enterprise systems, applications, APIs, and event sources, so coding agents build the integrations and UiPath governs credentials, actions, and events.
Every integration on UiPath composes three building blocks: activities (reusable read/write actions on external systems), triggers (event listeners that start workflows in real time), and connections (governed authentication, shared across activities and triggers). Teams configure these with a coding agent or visually in Studio.
Pre-built connectors cover systems including Salesforce, SAP, ServiceNow, Workday, Microsoft Dynamics, Google Workspace, and Slack. For systems without a pre-built connector, the HTTP connector calls any REST API and the webhook connector receives real-time events. Relay reaches private and on-premises systems from the cloud, and Connector Builder handles custom integrations.
Credentials sit in a centralized vault. Connections are reusable, scoped to UiPath folders, and protected by RBAC. Lifecycle management covers connector health, token refresh, and deprecation. Every credential access event, connection use, and trigger activation is captured in a full audit trail.
Integration Service is the connectivity layer. It provides activities, triggers, and connections that other products consume. API Workflows is a separate offering that runs automation logic as API-native backend services. The two work together: API Workflows can call Integration Service connectors when it needs external system access.
Yes. Integration Service is included with the UiPath Platform. See plans and pricing for the surfaces and limits at each tier.
