--- title: "Adobe Creative Cloud Libraries Integration" description: "Adobe Creative Cloud Libraries hold the colors, styles, images, and graphics a design team reuses across every Adobe app. Agents create and rename libraries, upload assets, update element metadata, search, and keep shared brand libraries current without opening Photoshop or Illustrator." url: https://flowrunner.ai/integrations/adobe-cc-libraries date_modified: 2026-09-04T19:38:13-07:00 --- # Adobe Creative Cloud Libraries [CMS & Content](https://flowrunner.ai/integrations/category/cms-content) Adobe Creative Cloud Libraries hold the colors, styles, images, and graphics a design team reuses across every Adobe app. Agents create and rename libraries, upload assets, update element metadata, search, and keep shared brand libraries current without opening Photoshop or Illustrator. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 23 actions · OAuth · available [Adobe Creative Cloud Libraries website](https://cc-libraries.adobe.io/) · [Platform Documentation](https://github.com/AdobeDocs/cc-libraries-api-spec) · Capability data verified 2026-08-28 1. A brand refresh is approved upstream and the new asset set lands in the shared drive 2. Agent reads the approved files and the retirement list that came with them 3. Upload Asset puts each new file in place, and Create Elements gives it a representation 4. Search confirms the retiring elements are the ones actually referenced by name 5. Archive Elements moves the old versions out of the working set, reversibly 6. The diff posts to the design channel with what was added, archived and left alone 7. A brand owner reviews the archive list before anything is purged or a library is deleted ## What This Integration Enables Creative Cloud Libraries are where a design team's reusable material actually lives: the colors, character styles, images, videos and graphics that appear in every Adobe tool the team opens. That makes them a brand governance surface as much as a design one, and it is the reason automating them is worth doing. FlowRunner agents create, rename, copy and move libraries, upload assets and attach them as elements, update element metadata and representations, search across libraries and elements, and read publicly shared libraries by their public id without needing them added to an account first. Adobe drew a line inside this API that most platforms leave to the caller, and it is the line this page is built on. Deleting an element does not destroy it, it archives it, and Restore Archived Elements brings it back. Destroying an archived element is a separate operation with a different name. An agent can live entirely on the reversible side of that line and still do the work, which is what makes brand library maintenance a good candidate for [Orchestration as a Service](https://flowrunner.ai/concepts/orchestration-as-a-service) rather than a standing manual chore. ### Without FlowRunner **Stale kits in circulation**: Designers keep working from a library nobody remembered to update **Retirement by deletion**: Old assets get deleted outright because archiving them is another manual step **Kits assembled by hand**: A client brand kit is rebuilt in Creative Cloud from a folder every time it changes ### With FlowRunner **Kits current by default**: New approved assets are uploaded and attached as elements as soon as they are signed off **Retirement that is reversible**: Retiring an asset archives it, and restoring it is one call rather than a re-upload **Kits assembled from the source**: Libraries are built and refreshed from the system that already holds the approved files ## Use Case Scenarios ### Publishing an approved asset without opening an Adobe app A logo lockup or product photograph clears review in the approval system. The agent calls Upload Asset with the file, then Create Elements to attach it as a representation, because an uploaded asset is not visible in the library until an element carries it. Where the sequence involves several steps that depend on each other, Apply Batch Operations runs them in one call and lets a later request reference a value from an earlier response, so upload, create and set metadata happen in order without round trips. A note posts to [Slack](https://flowrunner.ai/integrations/slack) telling the design team the kit has changed and what changed in it. ### Keeping a client brand kit and a working file set in step An agency keeps client assets in a shared drive and its design tokens in a system of record. On a schedule, the agent calls List Libraries and List Elements to read the current state, compares it against the approved set, and reconciles the difference: Upload Asset and Create Elements for what is new, Update Element Metadata for names that changed, and Archive Elements for what has been retired. When a client asks to see the kit, Get Public Library and List Public Library Elements render it from the public id without anyone being added to the Creative Cloud account. ### Auditing what a team is actually reusing A quarterly sweep calls Search across libraries and elements for the naming patterns that mark deprecated brand material, using exact name matching where the audit needs precision and partial query matching where it needs coverage. The results go into a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with the library each hit belongs to, so the brand owner can see which retired assets are still sitting in kits that designers open every day. Nothing is removed by the sweep. It only reports. ## Human-in-Loop Highlight Adobe made most of this connector safe to automate by making deletion reversible, which is exactly why the two operations that are not reversible deserve a person. Delete Library is the sharper of them: it does not archive the library, it removes it, and everyone it was shared with loses it at the same moment. An agent running a tidy-up sweep across a hundred client libraries cannot tell from the API alone whether a library with no recent activity is abandoned or is the brand kit a designer opens on Monday. So the sweep stops and posts what it found: "Six libraries have had no element change in ninety days. Four are shared with two or more people. Deleting a library removes it for all of them, and Purge Archived Elements on the other two cannot be undone. Which of these should go?" The brand owner names them. The agent archives, restores and reorganizes on its own all year; the calls that take something away from somebody else belong to a person. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 23 actions ### Libraries 6 - **List Libraries** Lists the user's libraries. The owner setting decides whether shared and public libraries appear at all, and the selector decides how much of each library comes back, which is the difference between a light listing and a very large response. - **Get Library** Reads one library. Passing the version from a previous response returns Adobe's cached copy, which is how a polling flow stays cheap against a large library. - **Create Library** Creates a library, or copies or moves an existing one. Which of the three happens depends on which field is supplied, and exactly one behavior applies per call. - **Rename Library** Renames a library. It is the only field this route changes; elements and sharing are untouched. - **Delete Library** Deletes a library. Unlike deleting an element, this removes the library itself and everyone it was shared with loses it. This is the operation this page's human gate is built on. - **Apply Batch Operations** Applies a list of operations to one library in order in a single call, letting a later request reference a value from an earlier response. The expert route for sequences such as upload, create element, set metadata. ### Elements 5 - **List Elements** Lists the elements inside a library: colors, character styles, images, videos and other assets, filterable by mimetype and group. - **Get Element** Reads one element of a library, including its representations. - **Create Elements** Creates elements in a library, or copies and moves existing ones between libraries. Every element needs at least one representation, which is what holds its value, and an element created without one is rejected. - **Update Element Metadata** Updates top level attributes such as element names. It is deliberately limited to metadata, so representation data sent here does nothing. - **Update Element Representations** Replaces an element's representations, which is how its actual asset changes. The array is the complete list the element ends up with, so a representation left out is deleted and existing ones are sent back alongside the new. ### Archive 3 - **Archive Elements** Moves elements into the library's archive. This is reversible, which is what makes routine retirement safe for an agent to run unattended. - **Restore Archived Elements** Brings archived elements back into the library. - **Purge Archived Elements** Permanently destroys archived elements. The irreversible counterpart to Archive Elements, and the second operation this page holds for a person. ### Assets 1 - **Upload Asset** Uploads a file into a library and returns the reference an element's representation needs. The result is not an element on its own; it is fed into Create Elements to become visible in the library. ### Public Libraries 3 - **Get Public Library** Reads a publicly shared library by its public id, without the user needing that library in their account. The route for showing someone else's shared brand kit. - **List Public Library Elements** Lists the elements of a publicly shared library. Paging is not available here, so the whole set comes back. - **Get Public Library Element** Reads one element of a publicly shared library. ### Bookmarks 4 - **List Bookmarks** Lists the user's bookmarked libraries: the public ones they saved and the collaborative ones shared with them. - **Add Bookmarks** Bookmarks one or more libraries. Which field is required depends on the bookmark type, and a submission whose id already exists is discarded silently rather than reported as a conflict. - **Update Bookmark** Updates a bookmark, for example to change the sharing role or the sharing and commenting permissions recorded on it. - **Remove Bookmark** Removes a bookmark. The library itself is untouched; only the user's saved reference to it goes. ### Search 1 - **Search** Searches across libraries and elements. Several parameters are valid for elements only and are rejected rather than ignored alongside a library search. Name requires an exact match while a query string allows partial ones. ## Frequently Asked Questions ### What can FlowRunner do with Adobe Creative Cloud Libraries? FlowRunner agents can run List Libraries, Get Library, and Create Library in Adobe Creative Cloud Libraries, plus 20 more actions. ### Does connecting Adobe Creative Cloud Libraries to FlowRunner require OAuth? Yes. Adobe Creative Cloud Libraries connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Adobe Creative Cloud Libraries trigger a FlowRunner workflow automatically? Adobe Creative Cloud Libraries doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Adobe Creative Cloud Libraries?** This integration exposes Adobe Creative Cloud Libraries to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/adobe-cc-libraries. Site index: https://flowrunner.ai/llms.txt