a figma bot that gathers the handoff details

what a bot can do in Figma

a handoff can stall because a comment is unresolved, a component is unclear or the file has changed since the last review. give a bot a file reference and one of those questions. it can gather the details before anyone edits the design.

composio, the connection service dusk bot uses for apps, lists 53 Figma actions (catalog version 20261101_00, read 12 november 2026⁴). dusk bot treats 36 of them as reads, 2 as sends and the other 15 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like add a comment to a file: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Figma

1. open Connected apps in the sidebar.
2. pick Figma and sign in on Figma's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Figma.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

add figma in Connected apps, sign in through figma and choose which bot may use it. share the file reference and identify the frames that matter. for review work, allow reading actions first so a request to inspect a component does not become permission to alter variables.

routines to copy

use a separate routine for review feedback, implementation handoff and design references. the messages below produce private notes rather than comments posted into the file.

every wednesday at 11, read comments in the acme checkout figma file. group questions by frame and distinguish requests for a decision from small corrections. include the comment reference. draft an agenda here; do not post or react.

every thursday at 5, inspect the frames i named in the acme checkout file and list their components and styles. note where the available file data does not answer a handoff question. do not change the file or create development tickets.

on the first tuesday of each month at 9, read local variables and file versions for the acme design library. prepare a current reference list and identify the file version you inspected. do not claim a value changed unless you have evidence. leave variables untouched.

what it asks you first

a comment posted to figma is a send. it asks with Allow and Deny by default, unless you permit a daily sending amount. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending. keep the first review agendas in dusk chat if the bot should not speak in the file.

variable changes and other design data edits are different from comment posts. they may not ask first. leave those actions disabled for a review bot, or put "ask me before you change anything" into a routine that truly needs them.

what it cannot do

• promise arbitrary visual editing from this catalog. it includes variables and development resources, but no general action to draw or rearrange every layer on a canvas.
• post comments or change variables through a read-only figma grant. reading a file for a handoff is a smaller permission than maintaining its design data.
• start a routine the moment something changes in figma; there are no figma events, so these run on a schedule. local reviews also pause while the computer sleeps.

ask what the file actually establishes

an inventory can name a component without proving it is the right choice for the implementation. request frame references and mark unanswered questions explicitly. if those questions become work in linear, review the proposed issue before granting tracker writes.

a handoff is not an implementation

a github bot can read code context through its own connection, but a figma review alone does not establish what shipped. keep those sources distinct in the report. for export and campaign asset work, the canva integration has a different action list and different limits.