Gmail troubleshooting

important notice gmail v4 is currently in beta testing if you've already integrated it into your scenarios, it will remain available to you however, we strongly recommend against using gmail v4 for production environments due to potential breaking changes during the beta period for production use continue using gmail v2, which remains fully stable and supported for testing only gmail v4 beta documentation is available here we'll remove the beta label once we've incorporated user feedback and thoroughly tested the version explore the following error codes to help you build your {{scenario plural lowercase}} with gmail modules error 400 failed to verify a connection your connection has expired and is no longer valid you need to reauthorize the connection every seven days this error affects non google workspace accounts for more details, please refer to google oauth documentation https //developers google com/identity/protocols/oauth2#expiration due to google's updated security policy, unpublished apps can only have a 7 day authorization period after the oauth security token expires, the connection is no longer authorized and any module relying on it will fail solution option 1 to avoid weekly reauthorization , you can update the publishing status of your project if you update your project to the in production status, you will not be required to reauthorize the connection weekly change the status of your project by following these steps log in to the google cloud platform using your google credentials navigate to the oauth consent screen click the publish app button next to your app if the needs verification message appears, choose whether to go through the google verification process for the app or to connect to your unverified app currently connecting to unverified apps works in make, but we cannot guarantee the google will allow connections to unverified apps for an indefinite period for more information regarding publishing statuses, refer to the publishing status section of google's setting up your oauth consent screen help and our community page option 2 if you keep your project in the testing status, you will be required to reauthorize your connection in make every week reauthorize your google connection by following these steps log in to {{product name}} go to connections find your google connection and click the reauthorize button error 403 access denied you didn't add a test user for your project in google cloud platform, and the project has the testing status you need to add the email address associated with the google account you want to connect with make as a test user log in to the google cloud platform using your google credentials go to apis & services > oauth consent screen under test users , + add users and enter an email of a user that you want to create a connection for click save error 403 access not configured the gmail api was disabled in the google cloud platform you need to gmail docid\ v6l8kmmwflb2wxhoi3trp again