Find the relevant design screens faster
Turn an issue's design context into a clearer starting point by surfacing the relevant screens and structure from Figma.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
Action
Get file json
Get figma file data with automatic simplification. this enhanced version automatically transforms verbose figma json into clean, ai-friendly format with: - css-like property names - deduplicated variables - removed empty values - 70%+ size reduction use simplify=false to get raw api response.
Why this helps
A founder may spend their limited focus navigating a large design file to find the one screen mentioned in a new issue.
- Reduces navigation through large design files.
- Helps identify the screen or component connected to an issue.
- Makes early triage less dependent on remembering file organization.
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.
- 3In one instruction, tell Notis how to match a new public issue to a Figma file and report the most relevant nodes from the simplified file structure.
- 4Choose the Linear Public Team Issue Created trigger and a channel for run reports.
- 5Test with one real issue and verify the surfaced nodes correspond to its design context.
Questions about this workflow
Does this modify the file?
No. It retrieves simplified file data and reports relevant structure for triage.
What if the issue has no design reference?
The prompt should have Notis report that no confident file match was found instead of guessing.
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.