Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Adobe Commerce Details → Post Undefined

AI-generated

Overview

This node acts as a generic HTTP client for interacting with the Adobe Commerce API (formerly Magento). It allows users to send POST requests with a custom JSON body to any endpoint under the "Adobe Commerce Details" resource. This flexibility is useful when you want to perform operations not explicitly covered by predefined node actions, such as creating or updating entities with complex payloads.

Typical use cases include:

  • Sending custom data structures to Adobe Commerce endpoints.
  • Triggering specific workflows or integrations that require raw JSON input.
  • Extending Adobe Commerce functionality by calling less common or new API endpoints.

For example, you might use this node to post product details, update customer information, or submit order data by crafting the appropriate JSON body.

Properties

Name Meaning
Body The JSON payload to send in the POST request body. This should be a valid JSON object representing the data you want to submit to the Adobe Commerce API.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The parsed JSON response returned from the Adobe Commerce API after the POST request.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message instead of the expected response.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication credential for Adobe Commerce, including base URL and necessary tokens/keys.
  • The node uses standard HTTP methods and expects the Adobe Commerce API to be accessible via the provided credentials.
  • No additional external libraries beyond those bundled with n8n are required.

Troubleshooting

  • Common issues:

    • Invalid JSON in the "Body" property can cause parsing errors or API rejections.
    • Incorrect or missing API credentials will result in authentication failures.
    • Endpoint or resource misconfiguration may lead to "Resource not found" or "Operation not found" errors internally.

  • Error messages:

    • "No credentials returned!": Indicates missing or invalid API authentication setup.
    • "Resource Adobe Commerce Details not found" or "Operation Post Undefined not found": Suggests a mismatch between selected resource/operation and the node's internal configuration.
    • HTTP errors from the Adobe Commerce API (e.g., 400 Bad Request, 401 Unauthorized) will be passed through; check the API response for details.

  • Resolution tips:

    • Ensure the JSON body is correctly formatted.
    • Verify API credentials and permissions.
    • Confirm the resource and operation selections match the intended API call.
    • Enable "Continue On Fail" during testing to capture error details without stopping workflow execution.

Links and References

Discussion