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.

Hey, is anyone running their n8n workflows on Hostinger? I’m new to n8n/Hostinger and trying to hook up Google Sheets. The issue is Google won’t accept my Hostinger VPS IP as a redirect URI. I grabbed a domain through Hostinger but not sure how to tie it to the VPS. Anyone done this before? I couldn’t find any docs on it. Thanks!