CHILI publish partners
Acquia Connector for CHILI GraFx
Bring your approved Acquia DAM assets and their metadata into GraFx Studio, and produce print and digital content from the source. Designers place Acquia DAM images straight into design systems, and local teams get only the assets that match their market. Acquia DAM stays your system of record: no downloads, no re-uploads, no duplicate files.
The Acquia Connector for CHILI GraFx at a glance
What it does: Makes your Acquia DAM library available inside GraFx Studio. No downloads, no re-uploads.
Built by: CHILI publish, in partnership with Acquia.
Setup: Two steps. Get your connection details from your Acquia admin, then your CHILI GraFx admin installs the connector from the Connector Hub. No custom development. Follow the Acquia DAM Connector documentation for each step.
What the Acquia Connector does
The Acquia DAM Connector is a media connector built on the GraFx Connector Framework. It links GraFx Studio to your Acquia digital asset management (DAM) system, so the people who build and use your design systems work with approved assets from the source.
Browse your Acquia DAM assets: Acquia DAM appears as a media source in GraFx Studio, next to GraFx Media.
Let end users choose: link an image variable to Acquia DAM, and the people using the design pick from Acquia DAM assets.
Bring the metadata: Acquia DAM fields, such as a product name or a price, come with the asset. Map them to variables, so text in the design follows the image. [confirm]
Show each team the right assets: set a search query on an image variable, in the search syntax you already use in Acquia DAM, and users only get the assets that match. The query can be fixed, or follow another variable such as market or product line.
Keep your access rules: the connector signs in with credentials your Acquia admin issues. What those credentials can see is what GraFx Studio can see.
The connector brings assets from Acquia DAM into GraFx Studio. Your DAM management stays in Acquia DAM.
How the Acquia DAM integration works
Get your connection details: your Acquia admin creates the credentials for the integration in Acquia DAM.
Install: a CHILI GraFx admin adds the Acquia DAM Connector from the Connector Hub and enters those details.
Design: designers pick Acquia DAM as the media source, place assets, and set the search query for each image variable.
Produce: end users and automated runs create output from the design system, with assets coming from Acquia DAM.
What your team gets
Acquia stays the system of record
Your assets, metadata, and access rights stay in Acquia DAM. CHILI GraFx produces from them and doesn't replace your DAM.
No duplicate or outdated assets
Designers pull assets straight from Acquia. Nobody stores the same file twice, and nobody works from an old copy.
Local teams see only what's theirs
A regional marketer opens a design and finds the assets approved for their campaign, not the whole enterprise library.
What teams make with it
Local market campaigns: tie the search query to the market. Regional teams adapt the central design with the assets for their market only, in print and digital formats.
Product material: digital ads, in-store signage, and catalogs, where product details follow the product image through metadata.
Brand portals on top of Acquia DAM: in GraFx Experience Portals, franchisees, dealers, and store teams get a portal of their own, and the images in it come from Acquia DAM.
The first connector on the Connector Framework
The Acquia DAM Connector was the first connector on the open-source Connector Framework. CHILI publish built it in partnership with Acquia, and it was first shown at Acquia Engage London. Acquia's Deanna Ballew and Ward De Langhe, Chief Product Officer (CPO) at CHILI publish, walk through it in a CHILIpulse episode.
Acquia DAM and CHILI GraFx: who does what
Acquia DAM and CHILI GraFx do different jobs in the same stack. Acquia DAM governs your assets. CHILI GraFx turns them into finished content.
| Details | DAM Acquia | 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 Acquia DAM setup you already have.
Set up the Acquia DAM Connector for CHILI GraFx
Installing or configuring the connector? The documentation walks admins through each step, from the Acquia credentials to search queries on image variables.
Acquia DAM Connector documentation: configuration, authentication, image variables and DAM queries.
Connector Hub: how environment admins add and activate connectors.
Source code on GitHub: the open-source Acquia DAM connector, for developers who want to see how it works or build their own.
Speak to an expert: questions about your Acquia DAM setup or use case?
Frequently Asked Questions
What does the Acquia DAM Connector for CHILI GraFx do?
It connects your Acquia DAM to GraFx Studio. Designers and end users browse and use Acquia DAM assets, with their metadata, inside design systems.
How does the Acquia DAM integration with CHILI GraFx work?
Your Acquia admin provides the credentials. A CHILI GraFx admin installs the connector from the Connector Hub and enters them. From then on, Acquia DAM shows up as a media source in GraFx Studio. Sign-in for designers and for automated output can be set up separately.
Do we have to move or copy assets out of Acquia DAM?
No. Assets stay in Acquia DAM. GraFx Studio fetches them through the connector when a design needs them.
Can we control which assets local users see?
es. Designers set a search query on each image variable, for example a category. The query can be fixed, or follow another variable. See how DAM queries work.
Can finished content go back into Acquia DAM?
Yes, but not through the connector. Your systems can use the CHILI GraFx application programming interface (API) to generate output and store it in Acquia DAM.
Who built the Acquia DAM connector for CHILI GraFx?
CHILI publish built it on the open-source Connector Framework, and supports it. The source code is on GitHub.
Our other systems aren't Acquia. Can they connect too?
Yes. Any system with an API can have a connector, and developers can build their own. The Connector Framework page lists the ones available today.