See the design discussion when work shifts
When an issue changes, get the relevant Figma comments in view so open questions do not get buried across tools.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
Action
Get comments in a file
Retrieves all comments from an existing figma file, identified by a valid `file key`, returning details like content, author, position, and reactions, with an option for markdown formatted content.
Why this helps
A status or ownership change can restart work without anyone checking whether the design discussion still has open questions.
- Brings existing design feedback back into view after a change.
- Reduces manual searching through the file.
- Helps a new owner understand unresolved discussion.
Setup
Build it in a few focused steps.
- 1Connect Linear and Figma to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis conversationally to create one.
- 3Tell Notis in one instruction which issue changes matter, how to find the related Figma file, and to summarize unresolved design comments in the run report.
- 4Choose the Linear Public Team Issue Properties Updated trigger and a channel for run reports.
- 5Test with one real relevant issue change and check the summary against the file discussion.
Questions about this workflow
Does this change Figma comments?
No. It reads comments and summarizes design context in the Notis run report.
Can it cover private issues?
Use the private team issue properties trigger for issues in private teams.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Figma. A trigger fires from one place; an action lands in another.
Linear triggers
Figma actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a comment to a file
Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a reaction to a comment
Posts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id.
Comment Received Trigger
Triggered when a comment is received.
Create a webhook
Creates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`.
Issue Created Trigger
Triggered when a new issue is created.
Create dev resources
Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create, modify, or delete variables
Manages variables, collections, modes, and their values in a figma file via batch create/update/delete operations; use temporary ids to link new related items in one request and ensure `variablemodevalues` match the target variable's `resolvedtype`.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Delete a comment
Deletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Delete a reaction
Deletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Delete a webhook
Permanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible.
Connect any two apps with Notis in the middle.
Linear and Figma, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Figma.