- 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
Details
This is the first step of the submission process.
Please fill in all the necessary fields.
(50 characters max.)
This is one of the most important elements. It influences your reach on the Marketplace search results and represents the initial filter for Marketplace users when deciding if the listing has the potential to fit their needs. Please check the below best practices to guide you when picking one:
DOs |
DON’Ts |
The title should have the following structure {Capability} for {Software/System}E.g. Facial Recognition Model for Microsoft Azure When thinking of describing the listing use specific attributes that can help identify its exact purpose.E.g. converter, analyzer, validator, generator, manager If your listing is intended for a specific region include the region abbreviation.E.g. ESP for Spain, JPN for Japan, CA for California, NY for New York, etc. |
Don’t use abbreviations, generic, cryptic, or made-up words to describe your listing.E.g. Simple Data Extraction, Reliable Friend - Robot Pack It is not recommended to use special characters such as: / \ : * ? “ < > [ ] & $. These are not recognized during the search.E.g. Get_Valid_Files, Am I Online? |
This section allows for the uploading of a personalized image to be displayed on the listing's card, which should be reflective of the main concept of the listing and incorporate simplistic symbols. Additionally, it provides the option to include a company logo. If you do not include a listing image, the default image will be applied.
Image dimensions: 100X100
Don’t use images that you do not own the rights for. Make sure to follow the available brand guidelines of the application being integrated to.
(20 characters per tag max.)
Specify pertinent tags that will enhance the discoverability of your listing by end-users. Tags refer to terms associated with your listing that aid in searching for listings with comparable tags.
As a recommendation, it is advisable to divide tags into single words instead of using complete phrases, to streamline the search process.
For instance, if your listing is designed to operate with GSuite, potential tags may include docs, drive, email, Gmail, and GSuite.
If the tags are not provided by you during the submission, our team will add them based on the overall submitted information. However, we strongly believe it’s much more helpful when you add these yourself.
(200 characters max.)
Summarize your listing in a short phrase that will best explain what it is about.
DOs |
DON’Ts |
The summary should have the following structure {Action}{system interaction/what it interacts with}{purpose description}E.g. Validate XMLs against pre-defined schemas, Build attended processes quicker. In one concise sentence, clarify what the listing purpose is.E.g. Image analysis powered by Microsoft's Computer Vision service. Be specific about the listing utility or benefits. Include the listing type only if needed.E.g. Custom Activity allowing to save email files as a PDF. |
Don’t include the summary in the listing description area. The summary should not be expressed as a rhetorical question. You should not overuse generic descriptive adjectives or superlatives.E.g. Very easy, fun, perfect. Don’t include details about how the listing was created. Don’t mention any usage steps. |
Select the application(s) that your automation is developed for and works with. E.g. Excel, SAP, Outlook.
If the necessary application name is not on the list, type its name, press enter and we'll add it for you.
Don’t forget to click Next once you’ve added all the necessary information.