Skip to main content
If your organization uses a firewall to restrict access to your PSA, RMM, documentation system, or other integrated platforms, you need to whitelist Neo Agent’s IP address to ensure reliable connectivity.
This applies to any integration where your system is protected by a firewall or IP-based access control.

​
Neo Agent Static IPs

Add the following IP addresses to your firewall’s allowlist:
Add all of the addresses above, not just one. Different Neo services handle different work — verifying an integration when you connect it, and running the scheduled syncs afterwards — and they use different outbound IPs. Allowlisting only some of them produces an integration that connects successfully and then fails to sync, or the reverse.
If you don’t whitelist these IPs, Neo Agent may be unable to connect to your systems, resulting in failed syncs, API errors, or workflow interruptions.

​
Is an IP block actually your problem?

An IP block and a bad API key produce different errors, and the fixes don’t overlap. Neo’s error messages name which one you’re hitting:
Some platforms host the allowlist themselves rather than leaving it to your firewall, so Neo is blocked even though nothing on your own network is. IT Glue is the common one: Account → Settings → IP Access Control restricts both web login and API access to the addresses listed there. Lexful has the same kind of control under Settings → Platform → IP allowlist — if you use it, add the addresses above there too.

​
Where to Apply

You may need to whitelist this IP in several places depending on your setup:

PSA Systems

Autotask, ConnectWise, HaloPSA, and other PSA platforms that restrict API access by IP.

RMM Platforms

Datto RMM, NinjaRMM, ConnectWise Automate, and other RMM tools with IP restrictions.

Documentation Systems

IT Glue, Hudu, Lexful, and other documentation platforms with firewall rules or their own IP allowlist.

Other Integrations

Microsoft 365, Teams, Slack, and any other service with IP-based access controls.