Hi Maxim,Some CAT tools like memoQ, as well as others including web-based TMSs with a CAT component that are not client-based, allow an after-import and mid-project custom code execution step based on the selected workflow automation triggers. For such tools, as part of your workflow automation, you can write a simple script that will be parsing your XLIFF content based on specific elements and their tag attribute values, e.g. anything that is unlocked and empty, sending requests securely (and directly) to Google's AutoML Translation API and then serializing them back into the XLIFF file. That XLIFF file can be then used to update the project with whatever segments got translated - as part of the existing automation as well. This requires setting up environment variables correctly on the translation server for seamless authentication across multiple accounts. Google team did a great job offering all script samples for multiple programming languages. You just need to figure out the XLIFF parsing/serialization part really.
As far as third-party CAT plugins/connectors go (not to mention CAT tools themselves), you
must be absolutely sure your data is 100% safe and secure with them, since the reality is that they are 3-rd party SaaS companies that be adding another tier of data handling. If you are working with PII or SPI or/and have stringent NDAs
enforceable by frequent audits that explicitly disallow 3rd party data sharing such plugins is a no go as unfortunate as it may sound, since using existing solutions as an easy button even for an additional fee
instead of creating your own ones is always very tempting indeed especially for small and mid-size LSPs that usually lack programming experience or do not have budget for hiring an in-house development team.
Hope this helps.