Hi @shwetaP  You're right. It was the RC. We've whitelisted "inbound" ServiceNow IPs in the Meraki dashboard instead of the "outbound" IP range. Doing that, the Service Graph connector for Meraki has started working well.   Thanks a lot for your support on this topic. Ariel PS: Only a suggestion. Probably for people like me without knowledge on the Meraki Dashboard side, adding a note in the Meraki documentation saying this can help for other people configuring the connector. ... View more

Hi @GreenMan  Finally, it worked from Postman. Reading Meraki API documentation, I found this: The name to use is: "X-Cisco-Meraki-API-Key" in the Authorization for the API KEY value, and the URL is: https://api.meraki.com/api/v1/     ... View more

The Meraki doc is saying to use this URL: https://api.meraki.com/api/v1     ... View more

Using the API KEY in Postman  Status 200 OK And I have that answer for https://api.meraki.com/api-v1/get-organizations     ... View more

I'm following (really our Meraki admin is following) this doc from Cisco Meraki app published in the ServiceNow store: https://developer.cisco.com/meraki/build/servicenowservice-graph-connector-for-meraki/   Here you can see this:   And this   I don't have admin access to Meraki Dashboard. I can't validate how the API KEY was created and what role or permissions it has. I'm asking our Meraki admin.   Following the document, I saw this: https://developer.cisco.com/meraki/api-v1/get-organizations/ to do a test. In our configuration we have: https://api.meraki.com/api/v1 I believe we have a typo there. I changed to https://api.meraki.com/api-v1 and I'm retesting it.     ... View more

Hi @GreenMan  I was thinking about it just a few minutes ago. Let me try to validate if the API Key is working fine.   Thanks, Ariel ... View more

Hi @alemabrahao  I'll take a look and back with you. Thanks, Ariel ... View more

Hi Dexter, Thanks for the update. We just have started configuring the Service Graph connector in our ServiceNow dev instance. We have this error: Error in MerakiGetOrganization - orgStream: API Key missing access to organizations: 999999 (999999 is a fake number; there we're using our Organization ID (one of them, to validate the solution). Our Meraki admin provided us (I'm the ServiceNow Architect) the API KEY and confirm us it have read access (at least) to this organization.   Any idea to fix it? I've created a case for Meraki and a case in ServiceNow Support.   Thanks, Ariel ... View more

Hi Rafal,   Probably you should use more than "name" as "coalesce" in the transform map in ServiceNow, adding another field to make both a "unique identifier" (this works as a Primary Key for a table).   Doing that, when the transformation runs, it will decide based on name + other_field the uniqueness of the device and probably will create/update both separately.   I hope my answer can help you. Ariel ... View more