Bynder x Akeneo
Which Job Do You Need?
Overview of available jobs in the Connect Platform for the Akeneo & Bynder integration.
The Connect Platform offers several jobs, each designed for a specific purpose. Use the table below to identify which job matches your use case.
Job Overview
| Use case | Job |
|---|---|
| - Create or update metaproperties option in Bynder based on Akeneo product information: Bynder x Akeneo - Create Bynder options from Akeneo product data (Bynder Akeneo Connector) | |
| Apply rules to assets in Bynder | Bynder — Media rules |
| Send assets from Bynder to Akeneo, link them to products, and enrich asset meta-properties from Akeneo | Bynder medias to Akeneo assets |
| Link assets to products in Akeneo (if not handled by the previous job) | Akeneo — Asset/Product multi binding |
| Manage assets for Akeneo categories | Bynder medias to Akeneo assets — With Category binding |
| Manage assets for Akeneo Reference Entities | Bynder medias to Akeneo assets — With Record binding |
| Remove assets in Akeneo when they are deleted or archived in Bynder | Bynder — Remove assets |
Recommended Workflow
If you are setting up the integration for the first time, the typical job execution order is:
- Send Akeneo product data to Bynder — Populate Bynder meta-property options with Akeneo product data.
- Bynder medias to Akeneo assets — Transfer assets from Bynder to Akeneo, link them to products, and enrich meta-properties.
- Asset/Product multi binding (optional) — Link assets to products independently if step 2 did not handle it.
For specific use cases, add:
- Media rules — to apply automated rules to Bynder assets.
- With Category binding — to assign assets to Akeneo categories.
- With Record binding — to assign assets to Akeneo Reference Entities.
- Remove assets — to keep Akeneo in sync when assets are deleted or archived in Bynder.