About Orchestrator Integration Service Connect Builder

I want to manipulate custom objects in UiPath, so I built a connector from the Integration Service in Orchestrator and published it with the appropriate settings.

I was performing activity validation using the generated custom activity’s insert Record, but I encountered a redirect error with error code DAP-RT-1101 and cannot proceed further.

As a potential solution, I found that there seems to be a special flag called allow.automatic.redirect in the connect builder settings, but I couldn’t find it anywhere. The AI suggested that the only option is to use HTTP requests.

Is there a way to prevent the redirect error and use custom activities such as insert record?

Hello

Is the authentication using OAuth2’s Authorization Code?
If it’s an error related to the redirect, it seems that we should first check if that setting is correct. What do you think about this?
Alternatively, if there’s an authentication method that doesn’t involve redirects, that might also be an option to consider.

Hello!

The authentication method is Personal Access Token (PAT).

We are using a token connection that only has the necessary 4 permissions from private apps in HubSpot’s integrations.

Hello
With PAT, redirects shouldn’t occur during authentication.

Are other items, such as BaseURL, configured correctly?

The base URL is https://api.hubapi.com.

It seems there’s no problem.

Regarding the first POST mentioned:

This likely refers to the setting below, so are we checking to see if this can be configured to improve the situation?
(I believe this is something to be added individually)

Hi @once10201029,

The DAP-RT-1101 redirect error may be related to how the connector’s authentication flow handles redirects rather than the Insert Record activity itself.

I would first verify the authentication configuration in Connect Builder, especially if OAuth2 Authorization Code is being used. Also, check whether the redirect/callback URL configured for the connection exactly matches the URL expected by the external system.

If the connector requires a redirect that Connect Builder does not support/configure as expected, then using an HTTP Request can be a workaround, but I would first confirm the authentication and redirect configuration before moving away from the generated custom activity.

If you can share the authentication type and the exact DAP-RT-1101 error details, it may be easier to determine whether this is a connector configuration issue or a limitation/bug.