AI Automation Engineer Capstone Project

​@Rachel.G Change it to:

https://aa-community.cloud.automationanywhere.digital

That is what this field appears to want.

This looks like a callback URL mismatch rather than an issue with the Google Workspace setup itself. The response from the Automation Anywhere team confirms that this field expects the aa-community.cloud.automationanywhere.digital URL, so replacing the callback URL with that value should resolve the validation error.

One thing I’d also watch for in similar OAuth setups is making sure the callback URL configured in the external application matches the URL expected by the Control Room exactly. Even a small difference in domain, path, or protocol can cause the authorization flow to fail.

The same principle becomes important when integrating CRM and contact-center systems too, especially when evaluating Salesforce CTI options where authentication, routing, and external platform connectivity all need to work together. Salesforce CTI alternatives for call centers