Document How Problems Were Solved
When you close an issue, the solution code sits in Gist with no record of iterations or thought process. Notis fetches the solution Gist and shows all revisions, creating a history of how you solved the problem.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
You solve a problem but the iterations and learning are lost. Months later when a similar issue appears, you have to re-solve it because the thought process isn't documented.
- Solutions stay documented with evolution
- Faster resolution of similar issues next time
- Understand how problems were approached
- Build solution patterns for your team
Setup
Build it in a few focused steps.
- 1Connect Gist and Monday to Notis
- 2Create an automation named 'Issue Solution History'
- 3In the Prompt, write: 'When a Monday task is marked resolved or closed and references a solution Gist, fetch that Gist and list all its commits to show how the solution evolved'
- 4Set Trigger to webhook and choose your notification channel
- 5Test by closing a resolved issue that includes a Gist reference
Questions about this workflow
How does it know which Gist contains the solution?
Include the Gist link or ID in the resolved task. Notis will extract it and retrieve the revision history automatically.
Can it show diffs between revisions?
Yes. Notis displays the changes between each version, showing what was tried, what failed, and what finally worked.
What if there were many failed attempts?
That's valuable! The full iteration history shows your thinking, making it easier for someone else to understand the problem space and solution approach.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Monday to Gist. A trigger fires from one place; an action lands in another.
Monday 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'".
Get Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
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.
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.
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'.
List Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
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.
Monday 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.