Hi everyone,
I am scoping an integration for a client between Alteryx and UiPath running on Automation Cloud (post migration, Cloud Orchestrator + Identity Server).
They tested the official UiPath Tool connector and, from what I know, it simply does not work in their setup. I am aware the Gallery listing says v1.2.0 supports both on premises and Cloud Orchestrator (with AMP + DCM on Server), so my first question is whether anyone has the official connector actually working against Automation Cloud today, and if so, which connector version and Designer build. I have seen threads with "Failed to connect to platform" and "Parameters cannot be null" after UiPath side API changes.
If this will not work I am planning to skip the connector and call the Orchestrator REST API directly via the Download tool, so triggering processes, feeding queues and reading results. The integration logic itself is trivial. The real effort is the Automation Cloud authentication. A few questions on that:
- OAuth via an External Application (client_id / client_secret, client credentials flow) vs a Personal Access Token. What do people use in unattended Alteryx workflows?
- Token endpoint on Identity Server, plus the accountLogicalName and tenant in the URL and the X-UIPATH-OrganizationUnitId (folder) header. Is there anything that is not obvious here?
- Token expiry and refresh handling inside a long running or scheduled workflow.
Beyond those points, are there any other nuances or problematic things I should be aware of before I commit to the REST route? Has anyone done this on cloud based UiPath and can flag pitfalls worth knowing up front? Does the connector route do anything the raw REST route would not? Appreciate any real world experience.
