Oct 18 • General discussion
Parameterization of google nodes...can it be done?
I came across a video about parameterizing n8n nodes, which is really similar to what I do in my day job. The basic idea is to store configuration data in a database — in my case, I’m using Supabase with n8n — and then add a Supabase node at the start of the workflow to pull in the configuration for that flow.
The goal was to create a single checkAvailability flow that checks for open slots in Google Calendar, instead of having to build separate versions for each client. I had no problem pulling data from Supabase into the n8n workflow, but I hit a wall with the Google Calendar node — specifically, the authentication part.
I wanted to dynamically inject all the credentials and parameters so the workflow could connect to any client’s calendar. Sounded great in theory. Then I discovered the OAuth redirect URL is read-only. WTF. I tried pushing ahead anyway by using JavaScript to populate the client ID from Supabase, but no luck — the node apparently needs to authenticate at the time of creation or editing, which feels like a total showstopper for this idea.
Pretty frustrating. Has anyone found a workaround or managed to do something similar? The thought of manually cloning and managing dozens of nearly identical workflows hurts my brain.
0
1 comment
Parameterization of google nodes...can it be done?
powered by
skool.com/n8n-nodes-automation-lab-1570
Teacher: Top n8n creator
Learners: Everyone (Free Forever)
Suggested communities
Powered by