How to parse JSON array

I have a workflow which makes a web request to our MDM’s API. The MDM returns back a JSON list.

[
  {
    "device_id": "11111111-4498-4a16-b495-dd6ced251606",
    "device_name": "C01234567890-user1",
    "model": "MacBook Pro (16-inch, 2019)",
    "serial_number": "C01234567890",
    "platform": "Mac",
    "os_version": "14.0",
    "supplemental_build_version": "23A344",
    "supplemental_os_version_extra": "",
    "last_check_in": "2023-11-07T15:03:37.309525Z",
    "user": {
      "email": "user1@nuna.com",
      "name": "User 1",
      "id": 5,
      "is_archived": false
    },
    "asset_tag": "10000809",
    "blueprint_id": "11111111-4a1d-4d11-8cf3-53ab707b6336",
    "mdm_enabled": true,
    "agent_installed": true,
    "is_missing": false,
    "is_removed": false,
    "agent_version": "4.2.9 (4570)",
    "first_enrollment": "2021-05-21 16:36:45.787997+00:00",
    "last_enrollment": "2023-10-30 03:46:59.102587+00:00",
    "blueprint_name": "IT - Sonoma",
    "lost_mode_status": ""
  },
  {
    "device_id": "11111111-caea-4d25-a7b4-8e5d1d392530",
    "device_name": "987654321-user1",
    "model": "MacBook Pro (14-inch, 2021)",
    "serial_number": "987654321",
    "platform": "Mac",
    "os_version": "13.6",
    "supplemental_build_version": "22G120",
    "supplemental_os_version_extra": "",
    "last_check_in": "2023-11-22T04:47:35.872763Z",
    "user": {
      "email": "user1@nuna.com",
      "name": "User 1",
      "id": 5,
      "is_archived": false
    },
    "asset_tag": "10001000",
    "blueprint_id": "11111111-8127-475f-8a1c-0a64122b1458",
    "mdm_enabled": true,
    "agent_installed": true,
    "is_missing": false,
    "is_removed": false,
    "agent_version": "4.2.10 (4592)",
    "first_enrollment": "2022-02-17 21:49:56.252660+00:00",
    "last_enrollment": "2022-10-14 15:41:09.638548+00:00",
    "blueprint_name": "IT 2023 (Current)",
    "lost_mode_status": ""
  }
]

I want to specifically get the device_id from the object where asset_tag = 10001000.

Is there any way to do this purely in workflow automation?

I would normally do this with a simple FOR loop, but there doesn’t seem to be anything like that in the workflow options.

I think I understand how the JSONPath expressions work -- I managed to use https://jsonpath.com/ to refine my expression, but I’m stumbling on how to apply those expressions in the JSON Parser module.

am I putting this in the right place? is this how it should be formatted?

I’m trying to achieve this expression, but I don’t know where to put it.

$[?(@.asset_tag==`{{asset_tag_placeholder}}`)].device_id

I think I understand how the JSONPath expressions work -- I managed to use https://jsonpath.com/ to refine my expression, but I’m stumbling on how to apply those expressions in the JSON Parser module.

am I putting this in the right place? is this how it should be formatted?

 

I’m trying to achieve this expression, but I don’t know where to put it.

$[?(@.asset_tag==`{{asset_tag_placeholder}}`)].device_id

 

Your parser looks kinda weird. You can only use {{W2.response_body}} instead and use the serial number within the web request as a filter. The web request should just return a single object and not a full list so you have to edit W2. Can you share web request W2 with us?

The search term in my post above is from our mac deplyoment. We search the asset database in freshservice for the serial number of the mac device and then apply the asset name automatically to the mac. So quite similar.

Your other case: If your API doesnt allow for filtering this gets really complex. Not impossible though but really hard to handle. I’m talking of pagination. You get 30 assets/tickets or whatever back from your API call but the asset/ticket youre searching is on page 10 and not on the first one.

@alan_13300

I checked the API documentation from kandji. Is there a specific reason why you search for assets via email instead of using parameter for serial number?

Instead you could search for that serial number (e.g. entered via service request lookup field for assets) and your web request then just returns one single object so you can the use the parser (for the same value and not the 30th value depending on the position the returned asset is in) and extract the device id for that serial number to use its in any other web request or automation.

Parser node then only contains response boday wothout any params in the source.

@alan_13300

Yes I’m facing the same issue in some other scenarios. But they are planning to implement looping, I’ve seen some topics in the forum about that. No ETA as of now.

have you ever found an answer how to user placeholders in JSON path expressions?

Like your example:

$[?(@.asset_tag==`{{asset_tag_placeholder}}`)].device_id

I have the same requirement.