activities
latest
false
UiPath logo, featuring letters U and I in white

Integration Service Activities

Last updated Nov 18, 2025

About the Integration Service activities

The Integration Service activities are designed to use the connectors provided by Integration Service to create connections with third-party applications and enable automating them easily. This allows a faster integration into Software as a Service (SaaS) platforms.

We support a wide range of third-party applications, and the list keeps growing. This guide contains all of the activities created by UiPath® for use with Integration Service exclusively. Activities that use both Integration Service and Scope-based connections are documented separately in the Productivity Activities guide (for example, Microsoft OneDrive, Outlook, or Google activities) and IT Automation Activities guide (for example, Amazon WebServices, Azure, or VMWare).

Working with Integration Service activities

Studio Web

In Studio Web, the latest activities are available by default in the activity browser. For more information, see Adding activities to a project in the Studio Web user guide.

You can also use any available triggers to start your automation. For details, see How to start an automation.

Studio 2025.0.161

Starting with Studio 2025.0.161, Integration Service connectors are listed directly in the Manage Packages window. This makes it easier to add a connector and its activities to a project. For details, see Managing Connectors in the Studio user guide.

Studio Desktop version 2023.10 or higher

Starting with Studio Desktop version 2023.10, Integration Service activities are delivered through the unified UiPath.IntegrationService.Activities package.

All Integration Service activities and triggers are listed in Studio, in the Activities panel, in the Available section.

Note: Make sure you enable the Available filter in the Activities panel.

How to enable to Available filter in the Activities panel


Available Integration Service activities in Studio

When you add any activity from the Available list to your workflow, the UiPath.IntegrationService.Activities package is automatically installed as a project dependency. This gives you access to any connector from Integration Service, including your custom connectors.

Project dependencies in Studio includes the unified UiPath.IntegrationService.Activities package

UiPath.IntegrationService.Activities is a dynamic activity package, which means you don't have to manually update it. The activity package gets updated automatically. You always have access to the newest connectors, triggers, and activities, as well as the latest version of activities you are already using.

To learn more, see Frequently asked questions.

Tip:

To access preview activities, make sure that preview packages and activities are enabled. If you're using Studio Web, check out the Preview activities and packages section in the Studio Web User Guide. If you're using Studio Desktop, check out the Managing packages section in the Studio User Guide.

Studio version 2023.4 or lower

If you are using Studio 2023.4 or lower, use Package Manager to download individual activity packages for specific connectors. For details, see Managing activity packages in the Studio Desktop user guide.

Each Integration Service connector has a corresponding package available as UiPath.[ConnectorName].IntegrationService.Activities. For example, UiPath.Jira.IntegrationService.Activities.
Important: To benefit from the latest updates we bring to Integration Service connectors and activities, we recommend you upgrade to Studio 2023.10 or higher.

Project compatibility

All activities delivered through the unified UiPath.IntegrationService.Activities package are Windows and Cross-platform compatible.
 Windows - LegacyWindows Cross-platform
UiPath.IntegrationService.Activitiesnot availableavailableavailable

Standalone versions of Integration Service activity packages may also be Windows - Legacy compatible. Check individual package documentation to see the specific project compatibility.

Limitations

This section describes platform-level limits and other limitations that impact all Integration Service connectors and/or activities.

Data processing limits

Integration Service has a platform limit for retrieving responses. The maximum limit for data processing is 8 MB. This means that, for some API calls, the number of responses retrieved can exceed the 8 MB limit and throw the following error message: "Response content too large".

Note: The 8 MB limit applies to data in JSON format. This includes cases where files are sent or received in a Base64 format as part of the JSON data. For files handled outside of JSON, the limit is 1 GB.

Workaround

You can take the following steps to ensure the data processing limit is not exceeded:

  • Adjust the Max records field at activity level to a lower number.
  • Add filtering to your queries. Providing filter parameters can limit the number of responses.

Activity timeouts

There is a platform-wide timeout of 90 seconds for all activities based on Integration Service connectors. This means that if a response is not received from the API within 90 seconds, the activity fails with a timeout error.

Error codes

This section presents an overview of the error codes you might encounter using activities from the unified Integration Service activities package.

Error codes are in the range [1000, 3999], split in three categories:

  • Run time (RT) - [1000, 1999]
  • Design time (DT) - [2000, 2999]
  • General (can occur both at run time and design time) - [3000, 3999]

In error messages, the codes are displayed with the category prefix included, for example The “AccountId” field is required. DAP-RT-1003.

See the following table for descriptions of common error codes.

Error CodeCategoryMessageDescription
1001Run timeServiceProvider is null.A dependant service could not be loaded from the host activity.
1002Run timeConnection ID is empty.Connection ID not found in the activity.
1003Run timeThe "{fieldName}" field is required. A required activity argument does not have a set value.
1005Run timeService responded with an object that does not match the activity's output type. The response of an API call does not fit the output schema that was defined at design time.
1051Run timeTrigger execution failed.A trigger API call returned a failure code or the response is empty.
1052Run timeTrigger activity could not find any matches.A trigger ran in debug mode but no matches were found.
1101Run time Request failed with error: {0}. Status code: {1}. An API call failed on the Integration Service or vendor side.
1103Run timeNo custom message, the underlying exception message is displayed. An API call failed on the activity package side.
2000Design timeMetadata API request failed with error '{0}'. Status code: {1}. A metadata call failed. This is a call made by activities to Integration Service to get information about how they should look and behave.
2002Design timeThe object '{0}' is no longer accessible on the current connection. Please verify your permissions, or choose a valid object from this connection, or select a connection that includes this object. The credentials used to create the connection don't contain the object or the object was deleted.
2050Design timeQuery API request failed with error '{0}'. Status code: {1}. An API call failed to fetch data for a dropdown or another similar control. Possible causes:
  • The path constructed when invoking the element service is incorrect.
  • The vendor endpoint is down (typically returning a 502 code).
  • Missing scope to call the API properly.
  • The request looked for non existing key (returning a 404 code).
  • Missing header (returning a 400 code).
2151Design timeDuplicate field names "{0}" There are two objects with a similar name, e.g. ID and Id.
3000GeneralFailed to retrieve connection. Consider using a different connection. A call to the ConnectionClient component failed. Can have multiple causes, for example a connection that became invalid.
3004GeneralFailed to get access token for the resource {0}. Typically indicates the system cannot retrieve a valid security token, most often because an existing token has expired.
3005GeneralConnection is disabled. Please enable the connection to continue. The connection is disabled and must be enabled.

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.