Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Kandji Details → Post Undefined

AI-generated

Overview

This node integrates with the Kandji API to send custom POST requests for "Kandji Details." It allows users to submit complex JSON bodies that define field mappings, site mappings, and other criteria. This flexibility is useful for scenarios where you need to programmatically configure or update detailed Kandji settings or mappings in bulk.

Practical examples include:

  • Automating the setup of device management rules based on specific criteria.
  • Sending customized configuration data to Kandji to align with organizational policies.
  • Bulk updating or posting new mapping configurations without manual intervention.

Properties

Name Meaning
Body A JSON object representing the request body to be sent in the POST operation. It includes nested arrays and objects such as fieldmappings, sitemappings, and mappings_xtype. Users provide this JSON to specify detailed Kandji configuration data.

The Body property expects a JSON structure similar to:

{
  "fieldmappings": [{}],
  "sitemappings": [
    {
      "criteria": [{}]
    }
  ],
  "mappings_xtype": [
    {
      "field_mappings": [{}],
      "tag_list_pairs": [{}],
      "criteria": [{}]
    }
  ]
}

Output

The node outputs the JSON response returned by the Kandji API after the POST request. The output is structured as an array of items, each containing a json field with the API response corresponding to the input item.

If the API returns binary data (not indicated here), it would be included accordingly, but this node primarily handles JSON responses.

Dependencies

  • Requires valid Kandji API credentials configured in n8n (an API key or token).
  • The node sends HTTP POST requests to the Kandji API endpoint.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Invalid JSON in Body: If the JSON provided in the Body property is malformed, the node will fail. Ensure the JSON is correctly formatted.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key/token is correctly set up in n8n credentials.
  • API Endpoint Errors: If the Kandji API endpoint changes or is unreachable, the node will throw errors. Check network connectivity and API status.
  • Unexpected Response Structure: If the API response does not match expected formats, downstream nodes may fail. Inspect the raw output for debugging.

Common error messages:

  • "No credentials returned!": Indicates missing or misconfigured API credentials.
  • API error messages from Kandji will be passed through; review them for details like invalid parameters or permission issues.

Links and References

  • Kandji API Documentation (for detailed API usage and JSON schema)
  • n8n HTTP Request Node documentation (for understanding how HTTP requests are handled internally)

Discussion