CHILI publish partners
Bynder Connector for CHILI GraFx
Bring your approved Bynder assets and their metadata into GraFx Studio, and produce print and digital content from the source.
Designers place Bynder images straight into design systems, and local teams pick from approved collections when they adapt a design. Bynder stays your system of record: no downloads, no re-uploads, no duplicate files.
The Bynder Connector for CHILI GraFx at a glance
What it does: Makes your Bynder assets and their metadata available inside GraFx Studio. No downloads, no re-uploads.
Setup: An admin installs it from the Connector Hub and connects it with credentials from your Bynder admin. No custom development.
What the Bynder Connector does
The Bynder Connector is a media connector built on the GraFx Connector Framework. It links GraFx Studio to your Bynder digital asset management (DAM) system, so the people who build and use your design systems work with approved assets from the source.
Browse and place assets: Bynder appears in the GraFx Studio media panel. Designers place assets in a design without leaving the editor.
Let end users choose: link an image variable to the connector, and end users pick from approved Bynder assets when they adapt a design.
Bring the metadata: map asset metadata to variables, so text such as a product name follows the image.
Show the right collection: limit a variable to one Bynder collection, or let users browse collections as folders.
Keep your access rules: the connector signs in with credentials your Bynder admin creates. What those credentials can see is what GraFx Studio can see.
The connector reads from Bynder. It never adds or changes anything in your DAM.
How the Bynder integration works
Install: an environment admin adds the Bynder Connector from the Connector Hub in CHILI GraFx.
Connect: enter your Bynder address and the credentials your Bynder admin provides. The connector uses the OAuth 2.0 authorization standard.
Design: designers pick Bynder in the media panel, place assets, link image variables, and map metadata.
Produce: end users and automated runs create output from the design system, with assets coming from Bynder.
What your team gets
Bynder stays the system of record Your assets, rights, and approvals stay in Bynder. CHILI GraFx produces from them and doesn't replace your DAM.
No duplicate assets Nobody downloads a file to upload it somewhere else. Every design uses the asset from Bynder, not a copy.
Local teams produce on-brand content Designers decide which collection each design can draw from. Local teams choose from that set, inside design systems that carry your brand rules.
What teams make with it
Retail point-of-sale (POS) material: shelf talkers, posters, and store signs from approved product shots, in local languages and print-ready.
Local market campaigns: regional teams and retail partners adapt central campaigns for their market, in print and digital formats.
Brand portals on top of Bynder: in GraFx Experience, franchisees, dealers, and store teams get a portal of their own, and the images in it come from Bynder.
Victorinox: one Bynder DAM, more than 120 countries
Victorinox manages its brand assets in Bynder and operates in more than 120 countries. Its designers build design systems in CHILI GraFx from the company's own Adobe InDesign files and brand guidelines, with assets coming from their Bynder DAM. Local market teams and retail partners can then produce brand-compliant promotional and POS material without sending every change to the central design team.
Bynder DAM and CHILI GraFx: who does what
Bynder and CHILI GraFx do different jobs in the same stack. Bynder governs your assets. CHILI GraFx turns them into finished content.
| Details | DAM Bynder | Brand Execution CHILI GraFx |
|---|---|---|
| Its job | Manages your brand assets | Produces content from those assets |
| What it holds | Approved assets, metadata, rights, and approvals | Design systems with your brand rules built in |
| What you get from it | The approved asset | Finished print and digital content, in every size and market version |
CHILI GraFx is the Brand Execution Platform, not a DAM. It works on top of the Bynder setup you already have.
How to add the Bynder Connector to CHILI GraFx
See the setup steps above in action, from installing the connector in the Connector Hub to using Bynder assets in GraFx Studio.
Set up the Bynder Connector for CHILI GraFx
Bynder Connector documentation: installation, credentials and configuration.
Media connectors in CHILI GraFx: how media connectors work and how to build your own on the Connector Framework.
Speak to a CHILI GraFx expert: Questions about yout Bynder setup or use case?
Frequently Asked Questions
What does the Bynder Connector for CHILI GraFx do?
It connects your Bynder DAM to GraFx Studio. Designers and end users browse and use Bynder assets, with their metadata, inside design system
How does the Bynder integration work?
An admin installs the connector from the Connector Hub and enters your Bynder address and credentials. From then on, Bynder shows up as a media source in GraFx Studio.
Do we have to move or copy assets out of Bynder?
No. Assets stay in Bynder. GraFx Studio fetches them through the connector when a design needs them.
Does the CHILI GraFx connector change anything in Bynder?
No. It only reads. It doesn't add, edit, or delete assets in your DAM.
Can finished content go back into Bynder?
Yes, but not through the connector. Your systems can use the CHILI GraFx application programming interface (API) to generate output and store it in Bynder.
Can we control which assets local users see?
Yes. Designers can limit an image variable to one Bynder collection, or let users browse collections as folders. The credentials on the connector set the outer limit. Local users work in GraFx Experience portals or GraFx Studio.
Who built the Bynder connector for CHILI GraFx?
A third party built it on the open-source Connector Framework. CHILI publish reviewed and approved it for the Connector Hub.
Our other systems aren't Bynder. Can they connect too?
Yes. Any system with an API can have a connector. The Connector Framework page lists the ones available today.