Actions4
- Product Actions
Overview
This node allows you to create a new Product in Akeneo, a popular Product Information Management (PIM) system. It is useful for automating the process of adding products with detailed attributes, categories, groups, and pricing information directly from n8n workflows. Common scenarios include synchronizing product catalogs from other systems, batch uploading new products, or integrating Akeneo with e-commerce platforms.
Practical examples:
- Automatically add new SKUs from an ERP or e-commerce backend into Akeneo.
- Bulk import products with associated images, prices, and category assignments.
- Enrich product data by programmatically assigning them to groups and categories.
Properties
| Name | Meaning |
|---|---|
| SKU | The unique identifier for the product (required). |
| Family | The family code to which the product belongs. |
| Parent | The parent product identifier (for variant products; optional). |
| Enabled | Boolean flag indicating if the product is enabled (active) in Akeneo. |
| Categories | List of categories to assign the product to. Each entry contains a category value. |
| Groups | List of groups to assign the product to. Each entry contains a group value. |
| Price | List of price entries. Each entry includes: - priceValue: Numeric value of the price - coinValue: Currency code (e.g., "USD", "EUR") |
| File Path | Local file path to an image or media file to upload and associate with the product (optional). Example: /path/image.png |
Output
- json.response: Contains the response from Akeneo's API after creating the product. This typically includes details about the created product or error information if the operation failed.
- json.responseFile (optional): If a file was uploaded (via "File Path"), this field contains the response from Akeneo regarding the media file upload.
- In case of errors, json.message may be present with error details.
Example output:
{
"json": {
"response": { /* Akeneo product creation response */ },
"responseFile": { /* Akeneo media file upload response, if applicable */ }
}
}
Dependencies
- Akeneo API: Requires access to an Akeneo instance with REST API enabled.
- API Credentials: You must configure Akeneo API credentials in n8n (base URL, client ID, secret, username, password).
- File System Access: For file uploads, the n8n worker must have read access to the specified file path.
Troubleshooting
- Missing Required Fields: If "SKU" or other required fields are missing, Akeneo will return an error in
json.response. - Invalid File Path: If the "File Path" does not exist or is inaccessible, the node will fail when attempting to read the file.
- Authentication Errors: Incorrect or missing Akeneo credentials will result in authentication failures.
- API Limitations: Large payloads or too many requests may trigger rate limiting or validation errors from Akeneo.
- Error Messages:
json.messagemay contain error details from Akeneo, such as validation issues or permission problems.- NodeOperationError: Thrown for unexpected exceptions; check item index and error context for debugging.