Skip to main content
srmm0001
srmm0001
May 29, 2025
Question

UiPath Connected System Endpoint Setup — Stuck at Authentication or Folder Context

  • May 29, 2025
  • 3 replies
  • 0 views

Hi Community,

I’m currently trying to set up the UiPath Connected System (from the Appian AppMarket) to connect Appian with UiPath Orchestrator (Cloud) and trigger bots using the provided operations like StartJob, GetRobots, and GetReleases.

I’ve followed all instructions in the marketplace app and plugin, but I’m running into trouble when setting up the Connected System endpoint.

[emoticon:3c913c0db7eb4f9face51746da287257] My Setup:

  • UiPath Environment: Cloud (Community Edition)

  • Orchestrator URL:
    cloud.uipath.com/.../

  • Folder Name: folder1

  • FolderId (from URL): 585858

  • Tenant: DefaultTenant

  • Connected System Auth: Using email + password..............

3 replies

davidj137213
davidj137213
May 30, 2025

Could you share more information please? Do you see any error?

Do you have your robot published in your orchestrator and the credentials are correct?

srmm0001
srmm0001Author
May 30, 2025
i am facing issues while configuring the UiPath Connected System plugin in our Appian environment. The connection fails with the following error:
com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input
at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1]
Additionally, we encountered:
com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'Service': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
Troubleshooting Performed:
  • Verified credentials and access in UiPath Orchestrator (able to access via browser and Postman).
  • Confirmed Machine Key and Client Secret are correct.
  • Tried alternate URLs: with and without tenant suffix 
  • Plugin version: Latest from Appian AppMarket
  • Appian environment is cloud-based and up-to-date.
davidj137213
davidj137213
May 30, 2025

It seems that the json sent is not correct... let me try to replicate it please.

Terms & ConditionsAccessibility statement