Goal: Allow the native Google Calendar node to fully and reliably utilize the Google Service Account credential with the Impersonate a User feature for Domain-Wide Delegation (DWD).
The Problem/Use Case: I am building a workflow for a Google Workspace domain that needs to manage events across multiple user calendars (e.g., creating, updating, and reading events) in a secure, server-to-server manner.
Ideal Solution: Using the Service Account credential with DWD is the recommended, scalable, and secure method for automation in a Google Workspace environment, as it eliminates the need for individual OAuth credentials for every user.
Current Challenge: To achieve this, I am currently forced to use a complex setup involving the HTTP Request node to manually generate the required JSON Web Token (JWT) and construct the Google Calendar API calls. I also have to use expressions in the Service Account credential to dynamically set the User to Impersonate (e.g., {{ $json.user_email }}).
Why the native node is preferred: The native Google Calendar node is simpler to configure, manages all the API boilerplate, and provides a much clearer, less error-prone visual workflow experience. Using the native node prevents the need for the HTTP Request node entirely, which is the best practice for n8n development.
Request: Please ensure that the Google Calendar node fully supports and validates the Google Service Account credential when the Impersonate a User setting is active. This will bring the Google Calendar node into full feature parity with other Google nodes like Gmail and Google Drive, which already support this for DWD workflows.
Thank you for considering this enhancement!