The Log, for Real
Two scripts in the examples folder. The first calls Figma's REST API and writes a dated table of every version of a file: when, who, and why. The second sends one message to a Discord or Slack channel when you tell it to. Tonight neither credential is set, so the film is the setup.
The Log, for Real
Two scripts in the examples folder. The first calls Figma's REST API and writes a dated table of every version of a file: when, who, and why. The second sends one message to a Discord or Slack channel when you tell it to. Tonight neither credential is set, so the film is the setup.
Series: Figma for Educational AI Topic: FIGMA · VERSION LOG
Chapters
0:00 Introduction 0:23 Introduction 1:45 Your Turn
YOUR TURN
Your turn. Open Claude and say: I want to set up the version log script. Walk me through creating a personal access token in Figma Settings, with the file-versions-read scope, setting it as the Figma token environment variable, and running the script on my file key. Then check two things yourself. After running it: how many versions are named? And
@NikBearBrown
Part of the Figma for Educational AI series.
Sources and citations: see the reel's SOURCES.md in the open textbook.
▶ The full series playlist — Brutalist https://www.youtube.com/playlist?list=PLG9H-C6rp5RU
What this video covers
- 0:00 — Introduction
- 0:23 — Introduction
- 1:45 — Your Turn
Transcript
A lightly formatted transcript of the video, with timestamps so you can jump to any section on YouTube.
Introduction
[0:00] Kamusta, this is Liam in for Bear. Can an agent log what it changed in a Figma file? Better question, can it log and prove what it changed? Three terms: a version log, Figma's timestamped record of every save with the author's stated reason, a personal access token, a string from Figma settings scoped to reading file versions, and a webhook URL, a Slack or Discord address that accepts one incoming message.
Introduction
[0:23] Two scripts in the examples folder. The first calls Figma's REST API and writes a dated table of every version of a file, when, who, and why. The second sends one message to a Discord or Slack channel when you tell it to. Tonight, neither credential is set, so the film is the setup. For the version log, create a personal access token in Figma settings under security. Name it, pick the file versions read scope, and copy the value. Set it as the Figma token environment variable. The script reads it there and nowhere else. Never commit it, never paste it in a chat. For the notifier, you need one webhook URL. In Discord, open a channels integrations and create a webhook there. In Slack, install incoming webhooks and point it at a channel. Set
The URL in your shell. Dry run prints what would be sent. Add the send flag to deliver it. When the token is set and you run the script with a file key, it calls Figma's REST API, follows pagination, and writes a dated table. Autosaves have no label. Named versions have whatever the author typed. MCP edits appear under the signed in account, same as any person's edits. Pair the table with your session transcript to tell them apart. The verdict is pending. Tonight, neither token is set. The film is the setup guide. Pending Bear, creating the Figma token with the file versions read scope, running the script on the real version log file, and a webhook URL for one real send. The next film reports the real version count and the real message.
Your Turn
[1:46] Your turn. Open Claude and say, "I want to set up the version log script. Walk me through creating a personal access token in Figma settings with the file versions read scope, setting it as the Figma token environment variable, and running the script on my file key. Then check two things yourself. After running it, how many versions are named and do MCP edits show under your name? The log for real at Nick Bear Brown.
