Akeneo icon

Akeneo

Akeneo by pixelInfinito
Join our community

Actions4

Overview

The Akeneo node for n8n enables integration with the Akeneo PIM (Product Information Management) system.
For the resource Product and operation Patch, this node allows you to update an existing product in your Akeneo instance.
Typical use cases include synchronizing product data from other systems, bulk updating product attributes, or automating catalog management workflows.

Practical Example:
You have a product in Akeneo identified by its SKU, and you want to update its family, categories, groups, price, parent, enabled status, or upload new media information. This node lets you automate such updates as part of a larger workflow.

Properties

Name Meaning
SKU The unique identifier (SKU) of the product to update. Required.
Novo indentidicador(SKU) New SKU to assign to the product (if you wish to change it). Optional for patch.
Family The family code to which the product belongs.
Parent The parent product model code, if applicable.
Enabled Boolean flag indicating whether the product is enabled (true/false).
Categories List of category codes to assign the product to. Each entry is a string value.
Groups List of group codes to assign the product to. Each entry is a string value.
Price List of price objects. Each object contains:
- priceValue: Numeric value of the price
- coinValue: Currency code (e.g., "USD", "EUR")
Nome Product name to search for (not directly used in patch, but available).
File Path Path to a file on disk to upload as a product media file (optional; if provided, uploads the file after patching the product).

Output

  • The output will be a JSON object with a response field containing the result of the PATCH request to Akeneo's /api/rest/v1/products/{identifier} endpoint.
    • If a file was uploaded via "File Path", there will also be a responseFile field with the result of the media file upload.
  • In case of errors, a message field may be present with error details.

Example Output:

{
  "response": {
    // Akeneo API response for the patched product
  },
  "responseFile": {
    // (Optional) Akeneo API response for the uploaded media file
  }
}

Dependencies

  • External Service: Requires access to an Akeneo PIM instance with REST API enabled.
  • API Credentials: You must configure Akeneo API credentials in n8n (base URL, client ID, secret, username, password).
  • n8n Configuration: No special configuration beyond credentials.
  • Environment: If using "File Path" for media upload, the n8n worker must have filesystem access to the specified path.

Troubleshooting

  • Missing or Invalid SKU: If the SKU does not exist in Akeneo, the node will return an error message in the output.
  • Authentication Errors: Incorrect or missing credentials will cause authentication failures.
  • Invalid Category/Group Codes: Providing non-existent category or group codes will result in Akeneo API errors.
  • File Not Found: If the specified file path does not exist or is inaccessible, the file upload will fail.
  • Partial Updates: Only the fields provided are updated; omitting required fields may lead to validation errors from Akeneo.

Common Error Messages:

  • "message": "Not found" – The product with the given SKU does not exist.
  • "message": "Validation failed" – One or more fields did not pass Akeneo's validation rules.
  • "message": "Unauthorized" – Check your Akeneo credentials.

Links and References

Discussion