Hourly

Announce new versions of your design system

When someone saves a named version, the team sees its label and description without asking.

Runs: Hourly
Apps: Figma
AI: Not needed
Access: file_versions:read

Send this to your assistant

Create a ClickRuntime automation: every hour, check our 'Design system' Figma file and post any new named version to #design in Slack with its label and description.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

In a Figma team, saving a named version is how a designer says this is ready for review or handoff. Developers who wait for the final version, writers who need the latest copy and managers tracking milestones all depend on that signal, but Figma does not push it anywhere by default. People refresh the file, ask in chat, or build from an outdated version. The cost is rework on screens that were already superseded.

Every hour, ClickRuntime asks Figma for a file's version history, compares it with the last version it recorded, and posts any new version's label and description to your channel. The message appears soon after the designer saves, and the label explains what changed.

It suits teams where design milestones trigger work for others, such as engineering sprints or content updates.

What you get out of it

Start development from the right version
When a developer is told that version 2.3 is saved, they do not guess whether a file is final. That avoids building against screens the designer has already replaced. Building from the wrong frame wastes a day of engineering time. Designers get uninterrupted focus time, and the team still gets a clear answer.
Reduce status questions in chat
The channel message answers whether the design is ready. Designers stop being interrupted for confirmation, and everyone else stops refreshing the file hoping something has changed. Product managers can point stakeholders to it when asked what shipped when.
Keep a log of milestones
Each post includes the version name and description, so the channel becomes a timeline of design decisions. Months later you can find when a flow was first approved. Earlier review means mistakes surface while changes are still cheap.
Trigger review at the right time
Reviewers get a nudge when there is something new to review, not on a fixed meeting schedule. Feedback comes sooner and the next iteration starts earlier. Clear labels today save confused archaeology next quarter, when nobody remembers the context.
Encourage better version labels
When version notes are posted for everyone, designers write clearer labels. That small habit improves handoff quality across the whole team over time. Better notes help everyone who reads the history later, including you.

How it works

What happens, step by step

Every hour, ClickRuntime checks your Figma design system file for new saved versions.
It compares them with the last version it saw, so each version is announced once.
Each new version is posted to your Slack channel with its name, who saved it and its description.

Before it runs live

Connect Figma

What you get

RunsHourly

Announce new versions of your design systemtoday, 9:00Succeeded

Slack · #designDesign system: v4.2 by Priya New focus ring tokens, updated danger button

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Figma steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

file_version_published_alert.pyexample

from clickruntime import on_trigger, report_fetched, state, notify, http, credentials

FILE_KEY = "o5P6q7R8s9T0u1"  # your 'Design system' file

@on_trigger
def run(event):
    versions = http.get(f"https://api.figma.com/v1/files/{FILE_KEY}/versions", headers={
        "Authorization": "Bearer " + credentials.connection("figma", "main")}).json()["versions"]
    last = state.get("last_id")
    named = [v for v in versions if v.get("label")]
    new = [] if last is None else [v for v in named if v["created_at"] > state.get("last_at", "")]
    report_fetched(len(new))
    if named:
        state.set("last_id", named[0]["id"])
        state.set("last_at", named[0]["created_at"])
    if not new:
        return {"summary": "No new named versions"}
    for v in reversed(new):
        notify.slack(f"Design system: {v['label']} by {v['user']['handle']}\n{v.get('description') or ''}", channel="#design")
    return {"posted": len(new)}

FAQ

Common questions

Does it alert on every autosave?

No. Figma's version history includes named versions that people save on purpose, and the alert follows that list. Automatic checkpoints can be excluded so the channel only sees versions with labels. Only labeled versions are announced.

Can it watch several files at once?

Yes. Each listed file is checked in turn, and each new version is posted with the file name so the message makes sense. Keep the list to files that matter to avoid a noisy channel. That interval is easy to adjust.

How quickly will the message appear?

Within about an hour, because the check runs hourly. Teams that need a faster signal can shorten the interval to fifteen minutes, since Figma's version list is a lightweight request. Pick whatever interval suits your team.

What permissions does it need?

file_versions:read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it checks. Checks that find nothing new and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Every 5–10 minutes