- Release Notes
- Overview
- Getting Started
- Marketplace Vendors
- Marketplace Customers
- Publishing Guidelines
- Publishing Guidelines for Ready-to-go Automations
- Publishing Guidelines for Solution Accelerators
- Publishing Guidelines for Integration Service Connectors
- Security & IP Protection
- Other UiPath Listings
- Node-RED
- Setup
- Teams
- Microsoft Teams Scope
- Create Team
- Create Team From Group
- Get Team
- Get Teams
- Channels
- Create Channel
- Delete Channel
- Get Channel
- Get Channels
- Update Channel
- Chats
- Get Chat
- Get Chats
- Get Chat Members
- Messages
- Get Message
- Get Messages
- Get Message Replies
- Reply To Message
- Send Message
- Events
- Create Event
- Delete Event
- Get Event
- Get Events
- Users
- Get User Presence
- How It Works
- Technical References
- Get Started
- About
- Setup
- Technical References
- Azure Form Recognizer Scope
- Activities
- Analyze Form
- Analyze Form Async
- Get Analyze Form Result
- Analyze Receipt
- Analyze Receipt Async
- Get Analyze Receipt Result
- Analyze Layout
- Analyze Layout Async
- Get Analyze Layout Result
- Train Model
- Get Models
- Get Model Keys
- Get Model Info
- Delete Model
- Connectors
- How to Create Activities
- Build Your Integration
Marketplace User Guide
Overview
A connector is an inbound automation solution that resides outside of the UiPath product platform. Using HTTP requests, a connector enables you to invoke or retrieve information about UiPath resources from within your technology platform (e.g. start a job, add a Queue item, get environment status, etc.).
Connectors give you the flexibility to stay connected to your UiPath resources form outside of the UiPath products. So, if you want to invoke or retrieve information about a UiPath Orchestrator resource from within your application (e.g. start a job, add a Queue item, etc.), then a connector is the ideal integration to build.
For example, let's say your application is an issue management system and you want a robot to run a specific business process after a user or system event (e.g., a new ticket is created). By integrating with the Orchestrator API via a connector, you have the ability to send requests that instruct a robot to run the business process that typically follows the event (e.g., escalate ticket based on its category, content, etc.).
The first step in building your connector is to get familiar with the Orchestrator API by reviewing the following resources:
If you're interested in jumping into using the Orchestrator API and for hands-on learning, start with the Orchestrator API Postman Collection. This collection handles the authentication/token refreshing and provides step-by-step information for the most common processes.
After familiarizing yourself with the Orchestrator API, the next step is to start building. To help you start, review the following tutorials and examples.
The tutorials are intended to provide further details about the common operations you can integrate into your connector. We recommend reviewing these pages before reviewing the examples so that you have more contextual information.
The following are links to connector application mockups. These mockups include an example user interface and the corresponding Orchestrator API requests for each input field.
The purpose of these examples is to further conceptualize the topics discussed in the Tutorials section.
Operation |
Examples |
---|---|
Authenticate | |
Start a Job |