Zapier IP addresses are not fixed for most traffic: Zapier runs on AWS us-east-1 with changing addresses. On Professional, Team and Enterprise plans, supported apps such as Webhooks by Zapier and API by Zapier can route through two static /28 ranges, and for a private app you ask Zapier support to turn them on. Free plan traffic never uses them.
The lookup above shows those ranges, plus the lists Make and n8n publish, each from the app's own help page.
Which Zapier traffic uses the static ranges
Only traffic from a paid plan, through an app that supports the static option. Anything else still comes from Zapier's changing addresses, so a firewall that allows only the static ranges will block it. Zapier's old static address for SQL databases has stopped working; paste it into the lookup and it shows as retired, with the ranges that replace it.
Allow the user agent header, not a region
Zapier's own advice for traffic outside the static ranges is to allow requests that carry its User-Agent header rather than a whole cloud region. A region rule lets in every other customer of that cloud too. If your endpoint takes webhooks, a shared secret or a signature check proves the caller far better than either; our webhook signature checker helps you test one.
Make and n8n
Make publishes a short list of outbound addresses for each zone, so pick your zone in the lookup and allow only that one. It publishes none for traffic into Make, because those addresses change. n8n Cloud publishes one shared list for all its instances and gives no notice before it changes, so allow every address on it and recheck it often.
