- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2024 06:22 AM
Hi Community!
I am trying to do some Discovery of Google Cloud without luck.
I have reviewed and ensured what is mentioned here is ok: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1516673
I get the error: "provided account id is neither a gcp folder nor a gcp project pattern name: google cloud platform (gcp) - validate service account"
I have checked the Pattern Debugger and do notice that the variable "folder_res" never get's populated and is just empty. My hypothesis of why this does not work...
I see that ServiceNow tries first the endpoint: "https://cloudresourcemanager.googleapis.com/v3/folders/" + folderIDValue" or this one as an fallback "https://cloudresourcemanager.googleapis.com/v2/folders/" + folderIDValue "
Since no Folder can be set-up in Google Cloud without Organization from my understanding (not a Google Cloud Expert), then it is no wonder why this fails as it explicitly tried an "/folder" endpoint...
For this Google Cloud it is only set-up "Projects".
Do anyone know this or have any experience with this?
Kind Regards,
Robin J 😊
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2024 06:58 PM
@Robin J_ folder is not needed. Are you giving a valid Google cloud project name? that's what is expected - you can see here. Google Cloud Platform discovery (servicenow.com)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2024 06:58 PM
@Robin J_ folder is not needed. Are you giving a valid Google cloud project name? that's what is expected - you can see here. Google Cloud Platform discovery (servicenow.com)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2024 01:59 AM
Thanks for confirmation 🙂 It also was a hardened mid-server here so it could not reach googleapis.com on port 443 so we must open a firewall here... so issue much more basic than I first thought 🙂