Review the FAQs to learn more about Connector Builder.

Is Connector Builder available on-premises?
Yes, Connector Builder is on-premises for both Linux and Windows environments. Ensure that you enable the Control Room Connector Builder Service check box in the installer during the installation process. For more information about the services, see Select Control Room services to automatically run at startup.
What is the license requirement for Connector Builder?
Connector Builder requires an Enterprise Platform license. Contact your Automation Anywhere account representative for licenses. For more information about the license, see Enterprise Platform.
Can Connector packages created in the Cloud Control Room be used on-premises?
Yes, you can use the packages created in the Cloud on-premises.
What is the pricing model for Connector Builder?

Connector Builder itself does not have a separate per-connector or per-transaction fee. This means you are not charged based on the number of connectors you build or the volume of data flowing through them.

Can I test how my connector interacts with live APIs before publishing it in Connector Builder?

Yes, Connector Builder provides a built-in testing option to validate the functionality of your connector before publishing. For more information, see Test custom connector.

Does Connector Builder support APIs that require cookie-based authentication?

No, Connector Builder does not support cookie-based authentication.

Are there any size constraints on the API definition file used by the Connector Builder?

There are no size limitations.

Does Connector Builder currently support SOAP APIs?

Currently, Connector Builder supports REST APIs. However, we are evaluating other protocols like SOAP and GraphQL.

Can users with necessary permissions modify any Connector Builder package, or just their own?
Users with the necessary permissions can edit all connector packages including the packages that other users create in the Control Room.
Can I publish a connector with only a subset of available actions, rather than the entire set?
You can disable actions in the connector as per the requirements and publish the package. The disabled actions are not visible in the published version of the connector. For more information about disabling actions, see Enable and disable action in Connector Builder.