I am currently working on a workflow that connects to CIPP Node. Problem I am running into is that I can’t get n8n to connect to the CIPP Node. I have validated my Tenant URL, Client ID, API URL and Secrets but I keep getting err_invalid_url error. I have disconnected all nodes prior to the CIPP node and continue receiving the error. It’s like it isn’t even rebuilding the url currectly. Anyone with any insight on something like this would be greatly appreciated. I am running a self-hosted N8N and CIPP. My project is to build automation process for onboarding/offboarding clients in 365 so I cut out some of the repetitive tasks.
Hey,
The err_invalid_url usually means the API URL format isn’t quite right. Few things to check:
-
Make sure your API URL doesn’t have a trailing slash (remove the
/at the end if it’s there) -
Confirm the URL format is like:
https://your-cipp-domain.com(no extra paths) -
Double-check there’s no extra spaces in the URL field
Since you’re self-hosting both, can you share:
-
What does your API URL look like? (you can hide the actual domain)
-
Are you accessing CIPP via HTTP or HTTPS?
-
Is CIPP running on a custom port?
Also, try testing the CIPP API directly with Postman or curl first to make sure it’s actually reachable from your n8n instance. Sometimes it’s a network/firewall thing with self-hosted setups.
Thank You for responding so quickly…. so I tried with postman and I do get a 401 unauthorized error. so I clear out everything my secrets in 365 and cipp and everywhere else and started over with it in postman and got 401 unauthorized again. Evertyhing was good until I did the API validation and keepss failing there. For the API URL https://cippXXXXX.azurewebsites.net I have tried that along with /api, /, and /api/AddUser I am truly at a point of wth.