Connect project updates with useful Gist context
Use a project update as a cue to see whether your Gists hold supporting notes or implementation details.
Trigger
Project Update Posted
Fires when a project status update is posted on the Linear project's Updates tab. Covers projects in both public and private teams — polls with the connected user's token.
Action
List Gists
Tool to list the authenticated user's gists or all public gists if called anonymously. Use after setting a valid GitHub token in headers.
Why this helps
Project updates can prompt follow-up work without bringing the underlying notes along.
- Makes related project notes easier to rediscover.
- Supports a more informed next step after status changes.
- Reduces manual context switching during project review.
Setup
Build it in a few focused steps.
- 1Connect Linear and Gist to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis to create one in plain language.
- 3Ask Notis in a single instruction to look for Gists related to each project update and summarize likely supporting context.
- 4Choose the Linear Project Update Posted trigger and a channel for run reports.
- 5Test by posting a project update with a distinctive phrase.
Questions about this workflow
Does this change the project update?
No. It checks for related Gists and reports context without editing Linear or Gist.
How can I make matches clearer?
Use specific project names or terms in updates and Gist titles or content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Gist. A trigger fires from one place; an action lands in another.
Linear triggers
Gist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Gist Star
Tool to check if a gist is starred. Use when you need to determine if the authenticated user has starred a specific gist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Gist Comment
Tool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'".
Comment Received Trigger
Triggered when a comment is received.
Get Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
Issue Created Trigger
Triggered when a new issue is created.
Get Gist Comment
Tool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Gist Revision
Tool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA.
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).
List Gist Comments
Tool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
List Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
List Gist Forks
Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Connect any two apps with Notis in the middle.
Linear and Gist, 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 Gist.