Assigned IP Addresses for Cloudn n8n

Hey, I’m building an automation for a customer.

Describe the problem/error/question

The problem is the customer’s IT team needs to enable IMAP and SMTP access on the Exchange server for use to use it, and their IT team wants to enable this only for our IP addresses. We’re using an n8n Cloud.
And therefore I want to know if your IP addresses are likely to change or if we remain static???

Thanks for your help.

1 Like

according to the n8n docs :

n8n Cloud’s outbound IPs are not static. The documentation explicitly says that Cloud “can’t guarantee static source IPs” because the infrastructure is dynamic and scales with demand.


[Cloud IPs]

For firewall whitelisting, your customer’s IT team would need to allow the full set of n8n Cloud outbound ranges,

Because these may change without notice, n8n recommends relying on strong authentication (IMAP/SMTP auth, TLS, app passwords, OAuth, etc.) rather than strict single-IP allowlists. If their policy requires IP-based restriction, they’ll need to maintain this full list and be prepared for updates.

2 Likes

Hi @jmichel Welcome!
The practical workaround here is to use self hosted n8n instance as if you need a proper static IP address that you can lend to your client.

1 Like

Yeah the cloud IPs aren’t static, n8n is pretty clear about that in their docs since the infrastructure scales dynamically. If the IT team absolutely needs to whitelist specific IPs then self-hosting is really the only reliable option here, you’d spin up an instance on a VPS or cloud provider where you control the IP and can guarantee it won’t change. Something like a small DigitalOcean droplet or AWS EC2 instance with an elastic IP works well for this, the n8n docker setup is pretty straightforward and you’d have a fixed IP to give them.

1 Like

THanks! ok will check that.

Thanks - this is clear.
Appreciate the help here.

1 Like

Your welcome! Let us know how your solution goes and if you have any more questions!