Resources · Make integration

Adobe CC Libraries Make integrationAutomate Adobe CC Libraries with Make.

Can Make keep an eye on your Creative Cloud libraries for you? The Adobe CC Libraries Make integration offers 9 modules: 4 scheduled triggers, 4 actions and 1 search. Designers and ops teams will find here how to link the account and build a first scenario.

Try the Adobe CC Libraries integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Adobe CC Libraries Make integration automate?

It links your Creative Cloud libraries to Make, the no-code tool where you build a scenario: a chain of modules, each module being one brick that watches, reads or changes something. Once connected, Make can spot new or edited libraries and elements, read or list elements, archive one, and upload an asset for you.

A design team that sees what changed. Watch Updated Elements picks up elements that were edited, and Get an Element reads each one so that a module from another app can post the news wherever your team follows the work.

A clean inventory of a library. List Elements returns what it finds as separate bundles (a bundle is one item passed from a module to the next), which you can copy into a spreadsheet app or review one by one. Archive an Element then takes out the pieces nobody should reuse.

Assets that land in the right place. When a file arrives in another app, Upload an Asset sends it on to Adobe CC Libraries, so the brand files your team shares stay in one spot.

The documentation does not describe these modules, so their roles here are inferred from their names, with no known field, format or limit. Check each one in the editor before relying on it, and reach for Make an API Call when the list falls short. n8n is another automation tool, and the n8n vs Make comparison puts the two side by side. To go further, see the Make training or the Make pricing page.

Connect

How do you connect Adobe CC Libraries to Make?

  1. 01

    Prepare your Adobe project

    You need an Adobe developer account and an active Creative Cloud account. In the Adobe Developer Console, create or open a project, click Add to Project, pick API, select the Creative Cloud Libraries API and choose OAuth 2.0 Web.

  2. 02

    Save the API and copy the keys

    Enter the callback URI https://www.integromat.com/oauth/cb/adobe-cc-libraries2, click Save configured API, then copy the Client ID and the Client secret that Adobe displays. Keep both at hand for Make.

  3. 03

    Create the connection in Make

    Add any Adobe CC Libraries module to a scenario and click Create a connection. A connection is your Adobe account linked to Make once and reused by every module of the app. Name it if you like, paste the two keys and follow the prompts.

First scenario

Your first scenario with Adobe CC Libraries

GoalWhen a new file shows up in another app, Make uploads it to Adobe CC Libraries as an asset.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module starts everything; here it comes from the app where your files arrive.

  2. 02

    Set up the starting app

    Search that app by name, pick its module and link your account with Create a connection. Fill its fields: once connected, Make lists the folders or objects it can read.

  3. 03

    Add Upload an Asset

    Click the + on the right of the first module, search Adobe CC Libraries and choose Upload an Asset. Map the file coming from the first module into it, with the connection made earlier.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can read the bundles each module received, then open your library to check that the asset is there.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, and switch the scenario on. Each run then counts operations on your plan: one per module and per bundle.

Triggers

What can start an Adobe CC Libraries scenario

4 modules start a scenario when something happens in Adobe CC Libraries. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Adobe CC Libraries as soon as it happens.

Adobe CC Libraries1Watch New Elements

Watch New Elements

triggerIn the docs only

Watch New Elements hands your scenario every element added to your libraries since the previous check, one bundle per element, ready for the next module. It is the natural starting point when something new in a library should set work in motion.

How it fires
Scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and never more often than that on the Free plan.
When to use it
A designer drops a new piece into the shared brand library and the marketing team should hear about it.
Watch out
Each element found is its own bundle, and every module after the trigger runs once per bundle, which adds operations to your plan.
Adobe CC Libraries2Watch New Libraries

Watch New Libraries

triggerIn the docs only

Watch New Libraries tells your scenario when a whole new library appears in the account, rather than a single element inside one. You receive one bundle per library, which suits work that begins when a project or a client gets its own space.

How it fires
Scheduled. Make asks Adobe for new libraries at each run of the scenario, so a library created just after a check waits for the next one.
When to use it
A new client project opens and its library should be added to your project tracker.
Watch out
The documentation does not describe what the bundle holds, so create a test library and click Run once to see it before mapping anything.
Adobe CC Libraries3Watch Updated Elements

Watch Updated Elements

triggerIn the docs only

Watch Updated Elements reacts to edits rather than additions: an element that already existed and has been changed comes out as a bundle. This is how a team learns that a shared asset moved on without anyone sending a message about it.

How it fires
Scheduled. The check happens on the scenario's schedule, not at the moment of the edit; a new scenario starts at every 15 minutes.
When to use it
A logo in the brand library is revised and the people using older copies should be told.
Watch out
Following edits and additions in two separate scenarios already uses the 2 active scenarios the Free plan allows.
Adobe CC Libraries4Watch Updated Libraries

Watch Updated Libraries

triggerIn the docs only

Watch Updated Libraries works at the level of the library itself: when a library you already have changes, the scenario receives it as a bundle. Choose it over the element watchers when knowing which library moved is enough, without the detail of what moved inside.

How it fires
Scheduled. Make checks the app on the scenario's schedule; on a paid plan that interval can go down to 1 minute.
When to use it
A client library gets reworked and the account manager wants a heads-up before the next review.
Watch out
To see the library's contents, add List Elements after it; that search returns elements one bundle at a time, and each bundle costs operations further down.
Modules

What the Adobe CC Libraries modules do

Adobe CC Libraries gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Adobe CC Libraries1

Archive an Element

ActionIn the docs only

Archive an Element takes an element out of active use, so shared libraries stay tidy without clicking through Creative Cloud one piece at a time.

When to use it
After List Elements has surfaced outdated items that nobody on the team should pick up anymore.
Watch out
The documentation says nothing about undoing an archive, so try it with Run once on a test element before letting a scenario archive in bulk.
Adobe CC Libraries2

Get an Element

ActionIn the docs only

Get an Element reads one specific element and passes its details to the next module, so the rest of the scenario works from fresh information. It acts on a single element, unlike List Elements, which can return many.

When to use it
Right after a watcher, to read the element that started the run before posting it to another app.
Watch out
Map the element from the previous module's bundle instead of picking a fixed one, or every run will read the same item.
Adobe CC Libraries3

List Elements

SearchIn the docs only

List Elements is the search of this app: it returns the elements it finds as separate bundles, zero, one or many, and the following modules handle them one after another. It gives you the full picture of what a library holds.

When to use it
Building an inventory of a brand library in a spreadsheet app, or picking items to archive.
Watch out
Plan for the empty case, since zero results is possible, and remember that each bundle multiplies the operations of the modules placed after it.
Adobe CC Libraries4

Make an API Call

ActionIn the docs only

Make an API Call covers whatever the other modules do not offer: it calls any endpoint of the Adobe CC Libraries API with the connection you already set up, so there is nothing new to authorize.

When to use it
A need that the listed modules leave out but that the Adobe API documentation describes.
Watch out
You write the request yourself, so keep the Adobe API reference open and test each call with Run once before switching the scenario on.
Adobe CC Libraries5

Upload an Asset

ActionIn the docs only

Upload an Asset sends a file from your scenario into Adobe CC Libraries, which spares your team a manual import each time a brand file turns up somewhere else.

When to use it
An approved visual, produced or received in another app, should end up in the library everyone draws from.
Watch out
On the Free plan, Make handles files up to 5 MB, so check the size of what you route here before going live.
Need help

Need help automating Adobe CC Libraries with Make?

A person reads every message.

FAQ

Adobe CC Libraries and Make: common questions

01Is the Adobe CC Libraries Make integration free?
Yes, on the Make side: Adobe CC Libraries is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits per month. On the Adobe side, you still need an active Creative Cloud account, whose price this page does not cover.
02What do you need to connect Adobe CC Libraries to Make?
Two accounts and one pair of keys. You need an Adobe developer account and an active Creative Cloud account. In the Adobe Developer Console, you create or open a project, add the Creative Cloud Libraries API with OAuth 2.0 Web, enter the callback URI given in the Make documentation, save, then copy the Client ID and the Client secret. In Make, you click Create a connection on any module of the app, paste both values and follow the prompts. That single connection then serves all 9 modules.
03Does the Adobe CC Libraries trigger work in real time?
Most likely not. The documentation lists 4 Watch triggers and no instant trigger, so they are scheduled: Make checks Adobe CC Libraries on the scenario's schedule instead of being notified of each change. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan, while paid plans go down to 1 minute. For a first test, Run once performs a check right away and shows the bundles received, a handy way to confirm the setup before switching the scenario on.
04What if an Adobe CC Libraries module is missing or a limit gets in the way?
Start with Make an API Call. It reaches any endpoint of the Adobe CC Libraries API with the same connection, so an action absent from the list can be built from the Adobe API documentation. The Make documentation lists no specific limit for this app and flags its own content as AI-generated and worth verifying, so test each module with Run once. The limits you are most likely to meet come from your Make plan: file size, execution time and the scheduling interval.
05Should you use Make or n8n for Adobe CC Libraries?
It depends on your setup more than on the app. On Make, Adobe CC Libraries comes with 9 ready-made modules, the scenario editor and access from the Free plan, which suits a team that wants to build without code. n8n is another automation tool where many apps also have a node, so check its catalog for Adobe CC Libraries before deciding. The practical criteria are where your other automations already run, which modules you need, and who on the team will maintain the scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations