How do you relay n8n in the cloud to an internal secure network?

Questions
1

So we have just started using n8n. Our instance is running in the cloud.
However, as it is outside of our network, I can’t have a workflow run scripts on the secure internal network.
I can’t be the only person to have this issue.
So for those of you in the same position, how have you resolved this?
(Azure vpn gateway is an option, but I’m trying to avoid additional costs)

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hi @Adrian_Coles Welcome!
Actually you cannot do that on n8n cloud, as they do not support any private VPN or ssh, but instead if that feature is something which is really required and is worth sacrificing the ease of integration of multiple platforms which n8n cloud provides, then you can consider a self hosted n8n.

Although you can try tunneling like cloud flare which is free, and there you can expose your endpoints so they remain hidden from the main network, and still will work like normal.

3

welcome to the n8n community @Adrian_Coles
I’ve seen folks use an internal API secured by IP allowlisting and mTLS/tokens for this. n8n Cloud calls the endpoints to trigger your scripts, keeping everything sensitive protected and off the public web.