Never Miss a Process Update
Your team playbooks live in Gist, but you never check for updates. Notis fetches the latest revision every week so you always have the current process, preventing confusion and rework.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Your team updates playbooks in Gist, but individual members follow outdated versions because they don't check for changes, creating inconsistency and mistakes.
- Team always uses current processes
- Catch process improvements immediately
- Reduce rework from outdated playbooks
- Consistent team execution
Setup
Build it in a few focused steps.
- 1Connect Gist to Notis and identify your playbook Gists (like onboarding, launch, or troubleshooting playbooks)
- 2Create an automation called 'Weekly Playbook Review'
- 3In the Prompt, write: 'Every Monday morning at 8am, retrieve the latest revision of our main team playbooks (list specific Gist IDs) and send me a summary of what changed since last week'
- 4Set Trigger to notis_cron for Monday at 8am, choose Slack, and save
- 5You can get Gist IDs by clicking 'Get my Gist IDs' in Notis or asking in a Slack message
Questions about this workflow
What if playbooks change multiple times a week?
Notis will list all commits since the last notification, so you see every change even if the playbook is edited frequently.
Can I get notifications for specific playbook updates, not just a weekly digest?
Yes. Set up a webhook-based automation to trigger whenever a playbook is committed to, for real-time updates.
How does it show what changed?
Notis highlights additions, deletions, and modifications between the latest revision and the previous one, so you spot changes instantly.
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.