If you are on n8n cloud, it appears n8n authenticates you using its own client-id and secret. There is a note about that in the documentation. The same credential types in the self-hosted docker version do have a place to fill in client-id and client secret.