Connector Builder FAQs

Review the FAQs to learn more about Connector Builder.

Is Connector Builder available on-premises?
No, Connector Builder is currently only available in the Cloud, but it will be available soon on-premises. However, you can use the packages created in the Cloud on-premises.
What is the license requirement for Connector Builder?
It requires an Enterprise Platform license. Contact your Automation Anywhere account representative and see Enterprise Platform, for more information.
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?

Absolutely! Connector Builder provides a built-in testing environment to validate your connector's functionality before publishing it. For more information, see Test custom connector.

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

No, not at the moment.

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

There are no inherent size limitations.

Does Connector Builder currently support SOAP APIs?

Currently, Connector Builder focuses on supporting REST APIs. However, the development team is actively evaluating the inclusion of additional protocols like SOAP and GraphQL in future releases.

Can users with necessary permissions modify any Connector Builder package, or just their own?
Users with the necessary permissions can edit all connector packages, not just the ones they originally created.
Can I publish a connector with only a subset of available actions, rather than the entire set?
Connector Builder platforms currently operate on an all-or-nothing basis for publishing actions.