Trigger Nodes → Microsoft Teams Trigger (webhook node)
The idea is:
Allow the Microsoft Teams Trigger (and potentially other webhook nodes) to override the default N8N_WEBHOOK_URL. Alternatively, add an extra environment variable N8N_PUBLIC_WEBHOOK_URL and allow webhook nodes to choose the new public url as an option.
My use case:
Our instance of n8n is kept private and not exposed to the internet. The MS Teams Trigger node requires a public url so we created a very small reverse proxy, just for MS Teams Change Notification payloads and exposed that. For it to work we had to set N8N_WEBHOOK_URL to point to the reverse proxy.
This works for MS Teams but other nodes/triggers rely on that webhook url and our proxy does not support those nodes. We also don’t want to support it as we have yet to come across another webhook (that we use at least) that requires a public url. If the Teams Trigger was able to override the N8N_WEBHOOK_URL we could unset N8N_WEBHOOK_URL and let the other webhook nodes only be accessible privately.
I think it would be beneficial to add this because:
It improves the privacy options when exposing n8n to the public internet by allowing some control over which webhooks are publicly accessible and which are not.
Any resources to support this?
Are you willing to work on this?
Yes but I raise it here as I’m unsure whether raising a feature request in Github will get the issue closed and asked to be raised here instead