The problem with this is. Isn't the tunnel url just temporary? Next time you log in it will be back to local host. So how can we use it to sustain long term and use it to connect n8n to other services? Still stuck on this problem

@Peter Hollis True. This is an amazing and very easy solution for testing and building out workflows that are just meant to be tested once and showcased. I've been trying to find a long term solution myself since I've tried self hosting n8n on my local pc and also through railway. Honestly hosting it on a 3rd party clouse does have it's issues that's why I'm trying to find how I can permanently change the url of localhost 5678. Installed it again today using npm

Also I already paid for railway starter plan for $5 + usage since render was giving me a lot of issues when I tried using it

Update: I solved it after a while of making this post. What I tried was publishing my instance from the Google project. It goes into review. Then come back to n8n and sign in. It will show a warning but you will be able to sign in now. Then you can go and change your project on google back to private and everything works after that