See What Changed in Your Documentation
Documentation evolves over time, and you need to know what changed from the last version. Notis fetches the previous Gist revision automatically so you can diff it against the new version.
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
When updating documentation, you can't quickly see what the version before looked like, so you risk losing important context or accidentally deleting useful notes.
- See before-and-after documentation changes
- Never accidentally lose documentation
- Track what information was removed
- Compare versions without manual Gist browsing
Setup
Build it in a few focused steps.
- 1Connect Gist and Monday to Notis (both need to be authorized in the portal)
- 2Create a new automation titled 'Documentation Revision History'
- 3In the Prompt field, write: 'When a Monday documentation task is updated or marked complete, retrieve the current Gist and fetch the previous revision so I can see what changed'
- 4Set Trigger to webhook, select email or Slack, and save
- 5To test, update a documentation task that links to a Gist you've edited before
Questions about this workflow
How far back will it show revisions?
Gist stores the full revision history. Notis can fetch any previous revision, but typically you'll want the most recent prior version for comparison.
What if I made multiple edits in one day?
Notis lists all commits with timestamps. You can ask it to show the revision from before the latest edit, or from a specific time like 'yesterday'.
Can I see a side-by-side diff?
Notis will highlight the differences between the current and previous versions in the notification, making changes easy to spot at a glance.
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.