Skip to main content

Managing Multiple Widgets

So far, we’ve only been talking about single, standalone widgets. For certain use cases, you might want to coordinate across instances of your widget within the same file! We've augmented the Plugin API to complement the Widget API seamlessly to with these use cases in mind.

WidgetNode.widgetId and figma.widgetId

Every WidgetNode is associated with its corresponding manifest.json "id" field and you can use the Plugin API to read this value to check if a given widget node belongs to your widget.

WidgetNode.widgetId and figma.widgetId
const allWidgetNodes: WidgetNode[] = figma.currentPage.findAll(node => {
return node.type === "WIDGET"

const myWidgetNodes: WidgetNode[] = allWidgetNodes.filter(node => {
return node.widgetId === figma.widgetId


If you want to find all of the widget nodes that match the same node.widgetId, you can use findWidgetNodesByWidgetId.

 findWidgetNodesByWidgetId(widgetId: string): Array<WidgetNode>


Using the Plugin API, you can read the syncedState of a given widget node via WidgetNode.widgetSyncedState.


Similar to pluginData, access to this data is widget specific! The synced state on each widget node will only be visible to widgets that have the same WidgetNode.widgetId.

You can then implement a voting widget that caps the maximum number of votes each user can make within in the file. Prior to registering a user’s vote, you can sum up the total number of votes the particular user has made by enumerating through all your widgets in the current file.

Here’s an example snippet of code that does this:

const { widget } = figma
const { Text, useSyncedMap } = widget


function CounterWidget() {
const votes = useSyncedMap<number>("votes")

return (
onClick={() => {
let numVotes = 0
figma.currentPage.children.forEach(node => {
if (node.type === "WIDGET" && node.widgetId === figma.widgetId) {
numVotes += node.widgetSyncedState[]

if (numVotes >= MAX_VOTES_ALLOWED) {
figma.notify(`You've already voted ${MAX_VOTES_ALLOWED} times.`)
} else {
votes.set(, 1)



Additionally, given a widget node, you can clone it with a custom synced state and synced map values using WidgetNode.cloneWidget.

interface WidgetNode {
syncedStateOverrides: { [name: string]: any },
syncedMapOverrides?: { [mapName: string]: { [key: string]: any } }
): WidgetNode

NOTE: every key in syncedMapOverrides will override the entire corresponding synced map, deleting all existing keys in the map. If you wish to preserve some of the keys in the map, you'll need to explicitly specify them in the override.

Similar to WidgetNode.widgetSyncedState, the is only supported for widgets that share the same WidgetNode.widgetId! Only you can call this function on your widget nodes.

When used in combination with the useWidgetId hook, this lets you create rich, multi-widget experiences like an Org Chart, where each Org Chart Item is its own widget.

Similar to WidgetNode.clone, the duplicate will be parented under figma.currentPage. If you are relying on the x, y or the relativeTransform of the original widget, make sure to account for the case where the original widget is parented under a different node (eg. a section).


Not only can you clone a widget with a new synced state and synced map values, you can also set the state on an existing widget matching the same node.widgetId using setWidgetSyncedState. This can be helpful managing multi-widget experiences where the user is able to update other widgets by taking an action on a single widget.

  interface WidgetNode {
syncedState: { [name: string]: any },
syncedMap?: { [mapName: string]: { [key: string]: any } },
): void