Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Ingram Micro Details → Post Undefined

AI-generated

Overview

This node integrates with the Ingram Micro Details API endpoint using a POST request. It allows users to send structured JSON data containing client mappings and import entities lists to the Ingram Micro service. This is useful for scenarios where you need to programmatically submit detailed configuration or import data related to Ingram Micro's services, such as syncing client information or importing entity details in bulk.

Practical examples include:

  • Automating the upload of client mapping configurations.
  • Importing lists of entities into Ingram Micro systems as part of an integration workflow.
  • Sending complex JSON payloads to update or create records in Ingram Micro platforms.

Properties

Name Meaning
Body A JSON object representing the request body. It includes two main arrays: client_mappings and import_entities_list. Each array can contain multiple objects defining the respective data to be posted. The property expects valid JSON input.

The default value for the Body property is:

{
  "client_mappings": [
    {}
  ],
  "import_entities_list": [
    {}
  ]
}

Output

The node outputs the JSON response returned by the Ingram Micro API after the POST request. The output is structured as:

  • json: Contains the parsed JSON response from the API call.
  • pairedItem: Links the output item to the corresponding input item index.

If the API returns binary data (not indicated here), it would be handled accordingly, but this node primarily deals with JSON data.

Dependencies

  • Requires an API key credential for authentication with the Ingram Micro API.
  • The node uses HTTP POST requests with JSON bodies.
  • Proper configuration of credentials including base URL and authentication tokens is necessary.
  • No additional external libraries beyond standard n8n helpers and request utilities are required.

Troubleshooting

  • No credentials returned!: Ensure that the API key credential is properly configured and connected in n8n.
  • Invalid JSON in Body: The Body property must contain valid JSON. Invalid JSON will cause parsing errors.
  • API Errors: If the API returns an error, the node will throw an error unless "Continue On Fail" is enabled, in which case the error message will be included in the output JSON.
  • Missing Required Fields: The API may require specific fields inside client_mappings or import_entities_list. Make sure to provide all mandatory fields according to Ingram Micro API documentation.
  • Network Issues: Check network connectivity and API endpoint availability if requests fail.

Links and References

Discussion