- Getting started
- For administrators
- RPA workflow projects
- Creating an RPA workflow from an idea
- Creating a project
- How to start an RPA workflow
- Managing project files and folders
- Connecting RPA workflows to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- Local setup for RPA workflow and app projects
- App projects
- Agentic processes
- Agents
- Solutions
- API workflows
- Tests
Studio Web user guide
API workflows help you build, manage, and scale real-time, system-to-system integrations through APIs.
Built on a fully cloud-managed, serverless infrastructure integrated into the UiPath Platform, API workflows provide tools, performance, and organization-level governance to execute API-based processes fast and securely, without manual infrastructure management.
API workflows meet the needs of different roles across your organization: automation developers can chain API calls and transform data, platform administrators can manage and secure integrations, and system architects can design composite services that are exposed as reusable APIs.
For example:
- As an automation developer, you can build workflows that automate order processing, sync customer data across CRM and ERP systems, or trigger notifications based on real-time events.
- As a platform administrator, you can centrally manage integrations or monitor performance, without managing infrastructure or worrying about runtime environments.
- As a system architect, you can abstract complex business logic into reusable, secure APIs that serve as modular building blocks, simplifying system integration and data protection.
IP allowlist
Communication within the UiPath platform is already secured and does not require separate allowlisting by customers.
Allowlisting is required only when API workflows communicate externally. Serverless robots and Integration Service send requests to systems outside the UiPath platform, so external endpoints must recognize their outbound IP addresses.
Which outbound path applies depends on how the external call is made:
| Activity type | Authentication method | Outbound path |
|---|---|---|
| HTTP Request | Manual | Serverless robots |
| HTTP Request | Connector-based | Integration Service |
| Connector | Not applicable | Integration Service |
| Communication path | Requires allowlisting |
|---|---|
| Within the UiPath platform (for example, between API workflows and Orchestrator) | No |
| API workflows using Serverless robots to reach external endpoints | Yes |
| API workflows using Integration Service to connect to external systems | Yes |
Add the following IP addresses to your allowlist to support external communication:
- Serverless static IPs—Allow Automation Cloud - Serverless robots to run API workflows and communicate with external endpoints.
- Integration Service IPs—Enable API workflows to communicate with external systems through Integration Service.