Google recently introduced new restrictions on how users can use their API. The restrictions will be in effect as of June 1st, 2020. The purpose of the new measures is to protect Google users from leakage or misuse of their personal data on Google. New restrictions are related to the Gmail and Google Drive apps. More info here.
To access restricted scopes, the connected service (Integromat or any other service that wants to access the user's data via the API) has to be verified and has to have a Letter of Assessment to prove that the service is secure and transparent about how they use the data. Integromat complies with all of Google’s requirements for access to restricted scopes, unfortunately, most of the third-party connected services in Integromat don't have the Letter of Assessment and therefore don't comply with Google terms. Because of that, we are not permitted to send data to these services.
There are a few exceptions where it is possible to send data to an unapproved third-party service that doesn’t have the Letter of Assessment and doesn’t violate any of these new restrictions.
We opted for the Domain-wide Installation exception. Domain-wide Installation is suited for G Suite users and this approach allows users to integrate unapproved services without any limitations. Simply speaking, if you are a G Suite user you don't have to perform any additional steps and can directly connect to unapproved services.
Other ways that are also not subject to the additional verification process are those that pertain to Personal Use and Internal Use. Both of these approaches are intended for advanced users and it requires users to create their own project in Google Cloud Console and their own OAuth client. The complete guide on how to do that is here. Personal use is suitable for @gmail.com or @googlemail.com users and Internal Use is intended for G Suite users that prefer to use their own OAuth client instead of using Integromat's.
Google Drive, Gmail, and Email (connected to Gmail account).
If your email address ends with @gmail.com or @googlemail.com your account is not a G Suite account. If your Google account ends with custom domain e.g. @my-company.com then it is a G Suite account.
If you want to integrate any other service than Google Drive or Gmail, you don’t have to do anything special to connect to your services that use your @gmail.com or @googlemail.com account to sign in. Just create a connection to the service in the regular way as described in the Connecting To Services article.
The changes only apply if you are integrating Google Drive or Gmail. If you want to connect to Google Drive or Gmail then you have to switch to G Suite or create a custom OAuth client (advanced option).
There is no required action.