Bynder
Give Bynder a creative automation upgrade and generate high-end print and digital campaign variants from approved assets at scale.
CHILI GraFx Connector Framework
Our Connector Framework enables you to build dynamic bridges that accelerate creative production, ensuring unmatched efficiency in delivering graphic production at scale.
Give Bynder a creative automation upgrade and generate high-end print and digital campaign variants from approved assets at scale.
Pull visual & data assets from Acquia DAM into your GraFx Studio projects. Create, automate, publish... all at Scale.
Maximize the value of your digital content by connecting Canto to CHILI GraFx's creative automation tools.
Pull assets from your Aprimo DAM into GraFx Studio – no downloads or uploads, and everyone stays on the approved version.
Maximize the impact of your assets on your organization’s success with the GraFx Connector for KeePeek/CHILI GraFx.
Seamlessly connect the Sitecore Experience platform to CHILI GraFx to create endless creative possibilities at scale.
Connect Adobe Experience Manager assets to CHILI GraFx and create on-brand campaign variants at scale.
We are constantly expanding our array of connectors to enhance our customers experience. Join this open-source movement and build one yourself.
The standard Creative Automation process relies on various resources typically managed within your martech stack, such as media assets from your DAM system, brand guidelines from your brand management portal, and data from systems like PIM, CRM, or CDP.
GraFx Studio’s composition model is specifically designed to integrate these resources from external systems for use in creative automation.
This is achieved through the use of a Connector, which links GraFx Studio to any external system capable of providing resources or data via an API. Connectors are open-source, community-built, and available for free on CHILI GraFx.
Designers need to make sure they are pulling the right variation of a file that they need of each image… for print, for social media, etc. With the Acquia DAM Connector, they get the correct file automatically. Your designers don’t even need to think about it.
Follow the link below to discover more about CHILI Partners. You'll be in good company working with us!
Clear, concise, and well written, the CHILI Docs provide everything you need to go into build mode.
Got a question or a proposition? We’re available to help and always ready to discuss ideas.
Once you open-source your Connector and publish it, we'll work with you like we do with all our Partners to get the word out.
We consolidated 7000 assets into 7 smart Templates
Tom Dijk
Managing Partner @ RGN
I think localization is a great use case, enabling your regional teams to grab their Smart Templates and then use the same images and data, translating it into the correct language. You can then efficiently distribute all of that content. It's an amazing use case, in my opinion.
Deanna Ballew
Senior Vice President, DXP & AI @ Acquia
We serve our clients around the world. How can we help you?
A connector brings external data sources in CHILI GraFx. Data sources could come from a DAM, PIM, CPD, DX, CMS,…
From a technical perspective, a connector is basically a javascript file implementing an interface.
Customers and partners: To make a connector available to our customers out of the box, connectors will have to be submitted to our connector GitHub repository. This means all customer/partner connectors that are made available out of the box, have to be open-sourced.
The connectors we make available come from a dedicated GitHub repository. GitHub will be used as the interface to submit, review and approve connectors. More about how to build a connector can be found in our documentation: Intro- CHILI GraFx Guides
Native connector (build by CHILI publish): CHILI publish
Partner connector (build by a partner or customer): partner or customer, CHILI publish does best effort to support
Custom connector (build by a partner or customer but not open-sourced): partner or customer, CHILI publish does best effort to support
Integration:
Use of the API and/or SDK to integrate GraFx applications into another solution. This solution could be a brand portal, workflow, DAM, PIM, etc.
The end-user is a user of the platform/solution GraFx is integrated into. So the user of an integration is NOT a GraFx user.
Connector:
A connector is used to pull in data/resources into GraFx Studio.
A connector can be complementary to an integration, but can also be used by GraFx users on the GraFx platform.
The end-user could be either a GraFx user or a user of the system GraFx Studio is integrated with.