Cloudinary Connector
Description
Hoping to unleash the full power of Cloudinary DAM? Have product families that share the same enriching assets?
Vincit’s Cloudinary Connector is here for you!
Images and attachments can be fully managed in Cloudinary and replicated into Akeneo, be it Enterprise or Community Edition. You can define the products and their attributes the Cloudinary asset should be linked to using Cloudinary contextual metadata. In the Enterprise Edition, you can also utilize native naming convention and product linking rules for linking.
If you receive for example an updated certification document, just overwrite the old one in Cloudinary and all your products linked to that certification document get the update automatically.
You can also define the default behavior in different circumstances. The default image format can be defined if you for example want to have all your images as PNG. The connection between Cloudinary and Akeneo can be trimmed to track only certain Cloudinary folders or public ID’s defined by regular expression.
General Information
The Vincit Cloudinary Connector listens to Cloudinary events and acts according to the connector configuration.
The use of the connector requires an Akeneo PIM instance, Cloudinary account and access between them (Akeneo API connection).
Contact us and we will help you with the account creation and / or PIM deployment.
Cloudinary Connector with Akeneo Enterprise Edition
In Akeneo Enterprise Edition the Cloudinary Connector can create new assets and update existing ones. The default asset family code and the medialink attribute code are defined in the connector configuration and the family code can be overridden using the Cloudinary contextual metadata.
Cloudinary Connector with Akeneo Community Edition
In Akeneo Community Edition the Cloudinary Connector can set the Cloudinary asset link to the value of an Akeneo text attribute (the connector does not upload binaries to Akeneo and thus can not use the file or image attribute types). On the contrary to the default Akeneo CE behavior, this allows you to have the same image or document linked to multiple products.
Migrating from another system (CDN, PIM, network drive…)
Do you already have all your precious product images and documents stored somewhere? We can help you migrate them into Cloudinary.
Who we are? What we do?
Read more at https://www.vincit.fi/en/what-we-do/product-experience-management/.
Documentation
Installation
The connection to Akeneo PIM is managed through the Akeneo PIM API and no installation into your Akeneo environment is needed.
Akeneo PIM API needs to be accessible from the internet to use the connector.
Cloudinary API environment details are needed to be able to connect your Akeneo PIM with the Cloudinary account.
When the default configuration has been defined, we can deploy your connector instance to open the flow between Cloudinary and Akeneo.
Usage
Whenever a tracked change is made in Cloudinary, the modified asset is transferred into Akeneo. In Akeneo EE, if the asset does not yet exist, it is created as a new one. If it exists, the media link is replaced with the new one from Cloudinary.
Cloudinary asset specific configuration is managed using the contextual metadata fields. With these it is possible to override the Akeneo asset family (in EE) and link the Cloudinary asset to one or more products. Each contextual metadata field represents a single configuration detail.
Metadata examples
Asset family definition syntax: assetFamily:<asset_family_code>
(for example to add asset to family “product_images” the metadata field would be assetFamily:product_images)
Product linking syntax: product_id:<attribute_code>
(for example to add the Cloudinary asset to the attribute “main_image” of the product with ID “t-shirt”, the metadata field would be t-shirt:main_image)