Have more option setting in Google Calender

[Huong_Cao]

Have new form to add, anyone what have to add it

[jabbson]

Hey @Huong_Cao hope all is well. Welcome to the community.

Is this an installed community node?

[Huong_Cao]

I don’t think so. I use Google Calender OAuth2 API

Have 3 options in Grant Type

[jabbson]

mine looks like this:

(notice the lack of fields like Auth URL and Access Token URL as well as the icon, which is missing on your screenshot).

Are you on cloud or self-hosted?
If latter, which version of n8n are using?

[Huong_Cao]

Yep, I know, yours is normal. And other service of google seem the same.
I’m using self-host with Version 1.101.1
It’s have new version and I’m trying update now

[jabbson]

Oh I see what you did there. You are connecting the custom OAuth 2 API credentials.

Are you doing it like that (and not via regular account) for a reason?
If for a reason, try these values:

Authorization Code
https://accounts.google.com/o/oauth2/v2/auth
https://oauth2.googleapis.com/token

in the scopes use whichever scopes you need, like

https://www.googleapis.com/auth/calendar https://www.googleapis.com/auth/calendar.events https://www.googleapis.com/auth/calendar.app.created https://www.googleapis.com/auth/calendar.events.owned

[Huong_Cao]

Thanks for your information. I don’t know what I choose in n8n that cause it.
I’ll try it and reply you as soon as possible

[jabbson]

OK, let me know if you need help

[jabbson]

Just to follow up on my previous message, there are a few ways to use credentials in n8n:

• With standard nodes, which require credentials, example. You would do that when standard node has functionality that you require.
• With HTTP Request node and predefined credential typs, re-using credentials, created by standard node, example. Use this when you need to extend the functionality, provided by standard node and use API calls, not covered by it.
• With HTTP Request node and generic credential type, example. Use this when there is no standard node providing a predefined credential type and you need to create auth with a service which isn’t already supported by n8n. This is where you tried to create your credentials.

To re-iterate, what you want to do is go with a standard node (which exists for G Calendar) and if some calls are not implemented, fall back to re-using credentials created with a standard node in HTTP Request node and Predefined Credential Type.

Hope it clears things up a bit.

[cutecatcode]

Hi there, what n8n version are you using?

[Huong_Cao]

Now it have trouble with Google Drive. Do you know what reason can cause it

[jabbson]

Hey @Huong_Cao

Are you using the

• default Credential type for Google Drive Node or
• Predefined Credential / Generic Credential Type in HTTP Request node

[Huong_Cao]

I using default Credential Google Drive and not using any other node that connect with that Credential. Last time I update or somehow it work as normal. Now it happen again

[jabbson]

Could you share your workflow as well as you type of install (cloud/docker/npm) and n8n version if self-hosting?

A typical default credential page for google drive should look something like this
(with an icon and the fields like on the image)

[Huong_Cao]

I’m using docker selfhost in synology with docker n8nio/n8n
As you see in picture, it same name as normal but have more option.
It may have trouble in some where.
It have same issue last time. But after upgrade it fixed.
Now it the same, I update to Version 1.102.4 and no more issue with same action.

I wonder I have to restart n8n on docker frequently to make it refresh

[jabbson]

Well, it shouldn’t be happening to begin with. How do you create credentials? Do you add the node to the canvas (something like Share a file) and in the configuration you choose credentials [1], or do you go to the space and click on Add in the top right corner and then add Credentials [2]?

[1]

[2]

[Huong_Cao]

i create credentials both in Overview or in node have same issue.
Now I can add it normal but not sure in furture it can cause again