All templates

Automated Coolors Brand Palette Sync

Every night, WebRun opens Coolors, reads the palettes in your brand collections, compares each colour against what is published in Notion, updates the hex values and the export format notes where they differ, and posts to Slack whenever a colour the team already uses has changed.

Runs on WebRun · Strict Lockdown policy
Every night at 10:00 PM WebRunorchestrates each step
1 Coolors read the brand palettes
2 Notion publish the current hex values
3 Slack flag colours that changed
In short

How do I keep my brand palette hex values current for the team?

WebRun opens Coolors every night, reads the palettes in your brand collections, and compares each hex value against the brand page in Notion. It updates anything that moved, date stamps the page, and posts to Slack when a colour already in use has changed, so the team always has current values.

  • The current hex values sit in Notion, date stamped, every morning
  • A changed brand colour reaches the design channel the night it changes
  • Developers stop guessing colours from screenshots and exports

Built for design teams · brand managers · front-end developers · creative agencies

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens coolors.co in a real browser with your saved login - no setup, no API keys.

  2. 1
    Coolors - read the brand palettes
    coolors.co
    WebRun in Coolors: read the brand palettes
    WebRun opens Coolors to read the brand palettes.
    • Open Coolors and go to the collections holding your approved brand palettes
    • Read every palette and the hex value of each colour in it
    • Note which project each palette belongs to and which export formats it is set up for
    • Compare tonight's values against the ones captured on the previous run

    Done when Every brand palette has a current set of hex values and a record of what changed.

  3. 2
    Notion - publish the current hex values
    notion.so
    WebRun in Notion: publish the current hex values
    WebRun opens Notion to publish the current hex values.
    • Open the brand colours page in Notion and update each palette's hex values
    • Keep the colour names and their roles, such as primary or surface, alongside the values
    • Record which export formats each palette is prepared in and where designers pick them up
    • Stamp the page with tonight's date so the team can see it is current

    Done when Notion shows tonight's hex values for every brand palette with a fresh date stamp.

  4. 3
    Slack - flag colours that changed
    slack.com
    WebRun in Slack: flag colours that changed
    WebRun opens Slack to flag colours that changed.
    • Post to the design channel when a colour already in use has changed value
    • Show the old hex and the new hex side by side with the palette it belongs to
    • Stay quiet on the nights where nothing moved

    Done when The design channel is told whenever a live brand colour changes.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
coolors.co
ScheduleRuns automatically on this cadence
Every night at 10:00 PM
DeliveryHow each run's result reaches you
Colour changes · Slack
OutputWhat each run produces - A nightly refresh of the brand colour page with current hex values per palette, plus a note of any colour that changed.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it change my palettes in Coolors?

No. WebRun reads your collections and publishes the values into Notion. Editing or deleting a palette stays in Coolors with the designer who owns it, so the source of truth is never touched.

How is this different from routing a palette for approval?

Approval happens before a palette is adopted. This run happens after: it keeps the approved values published where designers and developers actually look, so nobody rebuilds a colour by eye from a screenshot.

What if a colour changes after developers already shipped it?

WebRun posts the old and new hex side by side in Slack the night it changes, so the team hears about it while the change is small rather than finding a mismatch weeks later.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.