I have been caught with this issue for several days now. I’ve tried going through the forums and I don’t see a solution for it.
After a few hours, my working workflow gets an error saying error with gmail trigger: refresh token is required. I’m using the gmail trigger. The gmail trigger doesn’t allow me to use a credential where I can provide the client secret key and keep the authorization active. I feel like this is a common error, does anyone know the solution? The issue is resolved when I sign into Google again, but it will recur after about an hour.
I’m using the cloud version of n8n. When I add a gmail trigger, and go to create a credential, I get the form shown in my screenshot. When I try creating other credentials (Google Docs, Drive, etc), I see the form you have in your reply. But I can’t select these other credentials with the gmail trigger. N8N only shows me the form I showed in my original message when trying to create a credential for the gmail trigger.
I’ve been able to connect to other Google Oauth2 integrations, just not with the Gmail Trigger.
I see, what version is your instance on? I feel like this will be solved either by updating ore restarting the instance. I’m pretty sure you can do it in the admin panel.
I have not found a solution. I tried restarting the workspace suggested by @Grot and that didn’t help. I also updated the workspace to 1.99.0 beta and the issue is still there. Now, I only see a button to sign into Google without providing any details. The sign in is successful, but the token issue comes back after a short bit.
I am using 1.78.1. I had a cron type of job which running on a particular date but my token also being expired and raising issue.I also have no idea how I can overcome this issue.Need help if anyone can.I was also thinking that we might have service-account.json option in n8n credentials but in 1.78.1 version I can’t see this option as well only login with google.Not sure that service-account.json option is available in self hosted version of N8N via docker.
