Automated Adobe Color Palette Documentation
Every Monday, WebRun opens Adobe Color, reads the themes saved in your library with the hex values of every swatch, writes a dated palette reference into Google Drive so developers and non-Adobe teammates can read it, compares it against last week's file, and texts your design lead through Twilio when a palette was added or a colour changed.
How do I keep our brand colour palettes documented for the team?
WebRun documents your Adobe Color library every Monday. It reads each saved theme with the hex value of every swatch, files a dated palette reference into Google Drive that teammates without Adobe access can read, compares it against last week, and queues a Twilio text to your design lead when a colour changed.
- Developers get exact hex values without an Adobe login
- Every palette change is dated and traceable week by week
- The design lead hears about a colour change the Monday it appears
Built for design teams · brand managers · marketing agencies · front-end developers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
color.adobe.comin a real browser with your saved login - no setup, no API keys. -
1
Adobe Color - read every saved theme
color.adobe.com
WebRun opens Adobe Color to read every saved theme. - Open Adobe Color and go to your saved themes library
- Capture every theme with its name, the hex value of each swatch and the date it was saved
- Record the colour rule or harmony used where the theme shows one
- Note themes shared to a library your team uses, separately from personal drafts
- Skip themes you have marked as archived
Done when Every saved theme is captured with its name and the hex value of each swatch.
-
2
Google Drive - file the palette reference
drive.google.com
WebRun opens Google Drive to file the palette reference. - Write a dated palette reference into your brand folder in Google Drive
- List each theme with its swatches, hex values and the date it was created
- Keep the previous week's file so the palette history stays traceable
- Group brand palettes, campaign palettes and experiments into separate sections
Done when This week's palette reference is filed in Google Drive alongside the previous versions.
-
3
Twilio - text the design lead on changes
twilio.com
WebRun opens Twilio to text the design lead on changes. - Compare this week's palettes against last week's file
- Draft a short text for the design lead naming any theme added, renamed or changed, with the old and new hex values
- Queue the message for approval before it sends, since it goes to a real phone number
- Send nothing when no palette changed. WebRun never edits, deletes or publishes a theme in Adobe Color
Done when A change note is queued for the design lead, or nothing changed and nothing was sent.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it text people without my approval?
No. The Twilio change note is queued as a draft for you to approve before it sends, because it reaches a real phone. Nothing is texted on a week when no palette changed, so the message always carries news.
Does it edit or delete themes in Adobe Color?
No. WebRun reads your saved themes and copies the hex values out. Creating, renaming, editing and deleting a theme all stay in your hands inside Adobe Color.
Why file the palette outside Adobe?
So developers, copywriters and clients without an Adobe login can read the exact hex values. The Google Drive reference is dated each week, which also gives you a history of when a brand colour changed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.