Skip to content

CHILI publish partners

Keepeek Connector for CHILI GraFx

Bring your approved Keepeek assets and their metadata into GraFx Studio, and produce print and digital content from the source.

Designers place Keepeek images straight into design systems, and local teams pick from the folders set for their market. Keepeek stays your system of record: no downloads, no re-uploads, no duplicate files.

The Keepeek Connector for CHILI GraFx at a glance

What it does: Makes your Keepeek library available inside GraFx Studio. No downloads, no re-uploads.

Built by: Graphique Alliance.

Setup: Two steps. Get your connection details from your Keepeek admin or Graphique Alliance, then your CHILI GraFx admin installs the connector from the Connector Hub. No custom development. Follow the Keepeek Connector documentation for each step.

What the Keepeek Connector does

The Keepeek Connector is a media connector built on the GraFx Connector Framework. It links GraFx Studio to your Keepeek digital asset management (DAM) system, so the people who build and use your design systems work with approved assets from the source.

  • Browse your Keepeek folders: Keepeek appears as a media source in GraFx Studio, with the folders your teams know from Keepeek.

  • Let end users choose: link an image variable to Keepeek, and the people using the design pick from Keepeek assets.

  • Bring the metadata: Keepeek fields, such as a product name, come with the asset. Map them to variables, so text in the design follows the image.

  • Show each team the right folder: set a Keepeek folder on an image variable, and users only get assets from that folder. The folder can be fixed, or follow another variable such as market or product line.

  • Keep your access rules: the connector signs in with credentials your Keepeek admin issues. What those credentials can see is what GraFx Studio can see.

The connector brings assets from Keepeek into GraFx Studio. Your DAM management stays in Keepeek.

CHILI GraFx design editor with a Keepeek media picker open, offering ChillHome interior images for a personalized event card

How the Keepeek integration works

  1. Get your connection details: your Keepeek admin or Graphique Alliance gives you your Keepeek address and credentials.

  2. Install: a CHILI GraFx admin adds the Keepeek Connector from the Connector Hub and enters those details.

  3. Design: designers pick Keepeek as the media source, place assets, and set the folder for each image variable.

  4. Produce: end users and automated runs create output from the design system, with assets coming from Keepeek.

CHILI GraFx media panel with a dropdown listing GraFx Media and Keepeek Media - GA, the Keepeek connector selected

What your team gets

Keepeek stays the system of record

Your assets, metadata, and access rights stay in Keepeek. CHILI GraFx produces from them and doesn't replace your DAM.

No duplicate or outdated assets

Designers pull assets straight from Keepeek. 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: give each market or campaign its own Keepeek folder. Regional teams adapt the central design with those assets only, in print and digital formats.

  • Product material: catalogs, leaflets, and point-of-sale (POS) material, where product details follow the product image through metadata.

  • Brand portals on top of Keepeek: in GraFx Experience Portals, franchisees, dealers, and store teams get a portal of their own, and the images in it come from Keepeek.

Built in two days on the Connector Framework

Graphique Alliance, a CHILI publish partner in France, built the Keepeek Connector on the open-source Connector Framework. It took two days. Philippe Bezaguet, Sales Director at Graphique Alliance, tells the story in a CHILIpulse episode.

Keepeek and CHILI GraFx: who does what

Keepeek and CHILI GraFx do different jobs in the same stack. Keepeek governs your assets. CHILI GraFx turns them into finished content.

Choose a column to view
Comparison table
Details DAM Keepeek 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 Keepeek setup you already have.

Set up the Keepeek Connector for CHILI GraFx

Installing or configuring the connector? The documentation walks admins through each step, from the Keepeek address and credentials to folder settings and metadata mapping.

Frequently Asked Questions

What does the Keepeek Connector for CHILI GraFx do?

It connects your Keepeek DAM to GraFx Studio. Designers and end users browse and use Keepeek assets, with their metadata, inside design systems.

How does the Keepeek integration with CHILI GraFx work?

Your Keepeek admin or Graphique Alliance provides your Keepeek address and credentials. A CHILI GraFx admin installs the connector from the Connector Hub and enters them. From then on, Keepeek shows up as a media source in GraFx Studio.

Do we have to move or copy assets out of Keepeek?

No. Assets stay in Keepeek. GraFx Studio fetches them through the connector when a design needs them.

Can we control which assets local users see?

Yes. Designers set a Keepeek folder on each image variable. The folder can be fixed, or follow another variable. See the configuration options.

Can finished content go back into Keepeek?

Yes, but not through the connector. Your systems can use the CHILI GraFx application programming interface (API) to generate output and store it in Keepeek.

Who built the Keepeek connector for CHILI GraFx?

Graphique Alliance built it on the open-source Connector Framework.

Our other systems aren't Keepeek. 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.