Understand Why Past Decisions Were Made
When you revisit a technical decision months later, you've lost the context. Notis lists all commits to that decision Gist, showing you the evolution of thinking and exactly why the decision was made.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
Why this helps
You reopen an old technical decision and can't remember why the team chose that direction. You risk making the same mistake again or wasting time re-litigating solved problems.
- See the full reasoning evolution
- Never re-litigate solved decisions
- Understand constraints that existed
- Make informed changes based on context
Setup
Build it in a few focused steps.
- 1Connect Gist and Monday to Notis in the portal
- 2Create an automation named 'Decision History Review'
- 3In the Prompt, write: 'When a Monday task is reopened or labeled as decision-review, list all commits for the associated Gist to show the decision timeline and evolution'
- 4Set Trigger to webhook, select your notification channel, and save
- 5Test by reopening a past decision task and ensure it links to a Gist
Questions about this workflow
How does Notis know which Gist contains the decision?
Include the Gist link or ID in the Monday task. You can also create a task template that auto-populates the decision Gist reference.
Can it show the actual code changes between commits?
Yes. Notis can display diffs between versions, showing exactly what changed in the decision or approach over time.
What if the decision Gist has hundreds of commits?
Notis summarizes the commits chronologically and highlights the most significant changes, so you get context without information overload.
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.