Connector management in the studio

Hi team,

As we know, there are some differences between packages and connectors under the Manage Packages menu.

I want to understand the following items:

  1. How the connectors are upgraded

  2. How version management works

  3. How to view the connector dependency? Since it does not appear in the project dependency section and only shows in the activities panel, other users who open the code cannot easily determine which connectors are used.

Please help me understand these items and share your valuable insights.

Hi @tejaskumar.darji ,

Connectors are cloud-managed and updated automatically, with no version control available to users.
Packages are manually managed, allowing you to choose and control specific versions.
For connectors, dependency details are not easily visible and often need to be identified manually.

Hi @tejaskumar.darji

Let’s say you are using the Microsoft 365 connector in your workflow.

You add an activity like:
“Use Microsoft 365 → Send Email”

Connector upgrade

You don’t manually upgrade this connector like a package.
If UiPath updates the Microsoft 365 connector in the cloud, your workflow will automatically use the updated version. No action is required from your side.

Version management

Unlike activity packages:

  • You will not see version numbers for the Microsoft 365 connector
  • UiPath manages the versioning internally

So there is no need to select or manage versions manually.

Dependency visibility

In your project:

  • You will not see Microsoft 365 in Project Dependencies
  • You can identify it only if:
    • You see activities like “Use Microsoft 365” in the workflow
    • Or check connections in Integration Service

Hope this clarifies your query.

Thanks,
Christopher

Yes, this helps. But I feel like at least UiPath should show a list of installed connectors. Currently, there is no clue how many connectors the project is using, so that could be a feedback and improvement idea.

What do you think about that?

Feedback

Yes, I completely agree with you.

Having a centralized view of connectors used in a project would definitely make things much clearer, especially for teams and handovers. Right now, since connectors are only visible through activities or Integration Service, it’s not very intuitive to quickly understand the full footprint of a project.

For example:
if a workflow uses Microsoft 365, Salesforce, and Slack, there’s no single place in Studio where you can see all three listed together , unlike packages in Project Dependencies. You end up identifying them manually by scanning activities, which is not ideal.

So your suggestion makes a lot of sense:

  • A simple “Connector Dependencies” section (similar to packages)
  • Or even a summary view in Manage Packages → Connectors would be a big usability improvement.

Your idea of showing connectors similar to Project Dependencies sounds valid and practical. This would align well with how UiPath already handles packages and would improve overall governance.

This is definitely a good candidate for a product enhancement or feedback to UiPath.

Thanks,
Christopher