Library Pulse

About

When someone publishes changes to a Figma library, the people who use it usually find out by accident. Library Pulse closes that gap: the moment the library is published, it sends an update that lists exactly what changed, to Slack, by email or to Google Chat.

What the update includes

• The library's name and who published it
• The publisher's description, the note they typed when publishing
• Components, styles and variables that were added, modified or removed
• Your team's own message. In Slack it carries real @mentions that ping people or user groups.
• The publish time: in Slack, in each reader's own time zone; in email and Google Chat, in the time zone of the editor who saved the setup
• A link back to the file

Where updates go

• Slack: one to three channels, picked from a searchable list.
• Email: up to five addresses. Each address receives a confirmation email first and gets updates only after confirming, and every update carries an unsubscribe link.
• Google Chat: up to three spaces you belong to, picked after you sign in with Google. Library Pulse adds itself to them and posts each update as the Library Pulse app. In a space, mention @Library Pulse with help, stop or start.

A file sends to one of the three at a time; you can switch later. It watches the one file you choose, using your own access to that file, so you don't need to be a Figma team or organisation admin. Everyone with edit access to the file shares one setup.

Download

Library Pulse is free on the Figma Community.

Get Library Pulse on Figma Community

You will need

• Edit access to the Figma library file you want to watch
• The library published at least once: that is how the plugin identifies the file
• For Slack, a workspace where you can add an app
• For email, the addresses of people who want the updates
• For Google Chat, a Google account that is a member of the spaces you want. If your organisation uses Google Workspace, its admin may need to allow Chat apps.

Publishing libraries is a paid-plan Figma feature. Slack user groups need a paid Slack plan; mentioning people works on every plan.

How to use

1. Open the plugin in your Figma library file. It connects your Figma account (one quick browser confirmation the first time) and identifies the file on its own.
2. Choose Slack, Email or Google Chat.
3. For Slack, connect your workspace (your Slack admin may need to approve the app), then pick one to three channels. For email, enter up to five addresses; each one receives a confirmation email. For Google Chat, sign in with Google, then pick up to three spaces you belong to; Library Pulse adds itself to them when you save.
4. If you like, write a message to go with every update. In Slack, type @ to mention people or user groups.
5. Choose Save & Activate.

From then on, every publish of that file sends an update. To stop them, open the plugin in the file and choose Disable. If Slack, Figma or Google access is ever revoked, or an address hasn't confirmed yet, the plugin says exactly what needs attention.

Privacy policy

Last updated 8 October 2026 · Also on its own page

This policy covers Library Pulse: the Figma plugin and the service behind it, which connects to Figma and to Slack, email or Google Chat for you. Library Pulse is made and maintained by Rajat Garg.

What it can access

• In Figma, it asks only for permission to manage webhooks on your file, to check that you can access the file, and to read published component and style metadata, which is how it identifies the file. It never reads your designs or file contents. Inside the plugin it also reads your Figma user ID, to connect your account, and your name, which it only shows back to you in the plugin.
• In Slack, it can post messages and list the names of channels, members and user groups for its pickers. It never reads your messages.
• By email, it sends to the addresses an editor of the file enters, and only after each address has confirmed. It never reads anyone's mailbox.
• In Google Chat, once you sign in with Google, it can see which Google Chat spaces you belong to, to list them for you, and add the Library Pulse app to the spaces you choose. It also receives your Google account's email address and account ID and, for a Google Workspace account, your organisation's domain. It posts updates as the Library Pulse app, never as you. It can't read the rest of a space's conversation: Google Chat gives it only the messages that mention it or are sent to it directly, which it reads to answer help, stop and start, and doesn't store.

What it stores

• Your Figma user ID, and the access tokens Figma issues to Library Pulse
• For each connected Slack workspace: its ID and name, the Slack user ID of the person who connected it, and the token Slack issues to Library Pulse
• For each Google account that connects Google Chat: its account ID, email address and organisation domain, the Figma user ID of the person who connected it, the permissions they granted, the token Google issues to Library Pulse, and whether Google has since revoked it
• For each file that is set up: its key and name, whether it sends to Slack, email or Google Chat, the chosen channels, email addresses or Google Chat spaces (their IDs and names), the optional team message and its mentions, the Figma user ID of the person who set it up, whether its updates are on and, for email and Google Chat, the time zone of the editor who saved the setup, which the updates use to show the publish time
• For each email address: whether it is awaiting confirmation, confirmed or unsubscribed, when it was added and when it confirmed
• For each Google Chat space Library Pulse joins: its ID, name and type, the Google Chat user ID of whoever last added or removed the app, when that happened, whether the app is still a member, and whether updates there are paused
• A record of each publish received and each update sent: the file, the Slack channel, email address or Google Chat space, the time, and whether it was delivered. Confirmation emails are recorded the same way.
• For the pickers, a copy of your workspace's channel, member and user-group names, fetched from Slack again once it is more than ten minutes old
• While you connect Figma, Slack or Google, a sign-in record that hands your session to the plugin, valid for ten minutes
• On your computer, in Figma's storage for the plugin: a session token and your connection details

The Figma, Slack and Google tokens are encrypted at rest (AES-256-GCM). Your file contents are never stored, and the details of each publish are passed on to Slack or Google Chat or into the email, not kept.

How email is delivered

Emails are sent through Amazon Simple Email Service, part of Amazon Web Services, from its Sydney region. Amazon handles the recipient addresses and the message in order to deliver it. If a message bounces or is reported as spam, Amazon forwards the notice to the mailbox library.pulse@rajatg.in; replies to an update go there too. The confirm and unsubscribe links in every email name one file setup and one address and are signed, so they cannot be altered to act on another; confirmation links expire after seven days. To limit misuse, an address receives at most three confirmation emails a day and a file sends at most 150 update emails a day.

How Google Chat works

When you connect Google Chat, you sign in with Google and allow two permissions: to see the Google Chat spaces you belong to, and to add the Library Pulse app to a space. Library Pulse uses your sign-in only to list your spaces and to add the app to the spaces you pick. Updates are posted by the Library Pulse app itself, and Google Chat shows them as coming from an app. Google, which provides Google Chat, processes the messages it carries.

Library Pulse's use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to deliver the updates you set up. It is never sold, shared, used for advertising, or used to develop, improve or train AI or machine-learning models.

How it is used

Only to deliver the updates you set up and to fill the plugin's pickers. It is never sold, shared or used for advertising.

Where it is kept

The service runs on Vercel and keeps its data in a Supabase (Postgres) database. Access is limited to the maintainer. Vercel's operational logs record events such as a saved setup or a failed delivery, with identifiers like your Figma user ID, a masked form of an email address, a Google Chat space ID or a Google Workspace domain, and never your tokens.

Keeping and deleting it

• Library Pulse keeps this data until you ask for it to be deleted. Disable stops a file's updates and keeps its setup.
• The person who set up a file can also choose Remove Figma connection, which deletes the webhook Library Pulse registered on the file.
• Any editor of the file can remove an email address from its list. The unsubscribe link in any email stops updates to that address at once; adding it again sends a new confirmation, and nothing is sent until it is confirmed.
• You can revoke Library Pulse's access to your Figma account, and remove the app from your Slack workspace, at any time.
• For Google Chat, you can remove Library Pulse from a space (the space's Apps & integrations), pause it there by mentioning @Library Pulse with stop, and remove its access to your Google Account at any time. Switching a file to Slack or email removes its Google Chat spaces from the setup.
• To have your data deleted, email library.pulse@rajatg.in.

Changes and contact

Any change to this policy is posted on this page with a new date. Questions and data requests: library.pulse@rajatg.in.

Terms of service

Last updated 8 October 2026 · Also on its own page

By installing or using Library Pulse, you agree to these terms.

• Free. Library Pulse is free to use.
• Your use. Use it only with Figma files, Slack workspaces, Google Chat spaces and email addresses you are allowed to use, and follow Figma's, Slack's and Google's own terms. Add only the addresses of people who want the updates; each of them confirms before receiving anything. You are responsible for what your setup sends, including your team's message and its mentions.
• As is. Library Pulse is provided as is, without warranties of any kind. Updates can be delayed or missed, and the service can change, pause or end at any time.
• Liability. To the extent the law allows, Rajat Garg is not liable for any loss or damage arising from the use of Library Pulse.
• Stopping. You can stop at any time: disable it in the plugin, revoke its access to your Figma account, remove it from your Slack workspace or your Google Chat spaces, revoke its access to your Google Account, remove the email addresses, or use the unsubscribe link in any email.
• Changes. Any change to these terms is posted on this page with a new date. Using Library Pulse after a change means you accept it.

Questions: library.pulse@rajatg.in.

Support

Email library.pulse@rajatg.in. Say which library file it concerns, whether it sends to Slack, email or Google Chat, what you expected and what happened, and attach a screenshot of the plugin if you can. Never send tokens or passwords; I never need them.

Before you write

• If the plugin shows Reconnect Figma, or says Slack or Google Chat is disconnected, that access was revoked (or, for Google, the sign-in expired). Reconnecting with the button it shows (Reconnect Figma, Add to Slack or Sign in with Google) fixes it; nothing else was lost.
• If updates stop in one Google Chat space, check that Library Pulse is still in it (the space's Apps & integrations) and that no one paused it there; mentioning @Library Pulse with start turns updates back on.
• If an address hasn't confirmed, ask its owner to look for an email from Library Pulse, spam folder included. The confirmation link lasts seven days; after that, remove the address and add it again to send a new one.
• If a publish produced no update, open the plugin in the file: its status shows whether updates are paused, awaiting confirmation or failing to deliver, and what, if anything, needs attention.

The plugin's code is public on GitHub, where you can also report a problem under Issues.