Make documentation progress visible
A better README can be a meaningful product improvement.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Create Image
Tool to create a new image based on a template. use when you have selected your template and prepared modifications.
Why this helps
Documentation work is valuable but easy to overlook because it does not look like a conventional feature release.
- Recognizes documentation as shipped work.
- Creates a lightweight way to share improved onboarding.
- Helps founders build a habit of communicating maintenance work.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Supportivekoala to Notis once through the portal.
- 2Create an automation and tell Notis: When the GitHub README changes, create a Supportivekoala update card highlighting the documentation improvement.
- 3Select the GitHub Repository README Changed trigger.
- 4Choose a channel for run reports and test it with one README edit.
Questions about this workflow
Can it monitor a README in a specific directory?
Yes. Configure the GitHub trigger for the relevant repository location.
Can it focus on onboarding changes?
Yes. Mention onboarding in the instruction when that is the goal.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Supportivekoala. A trigger fires from one place; an action lands in another.
GitHub triggers
Supportivekoala actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Image
Tool to create a new image based on a template. use when you have selected your template and prepared modifications.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Template
Tool to create a new template for image generation. use after gathering template details.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
List Images
Tool to list images associated with the authenticated user. use after confirming authentication.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
List Templates
Tool to retrieve all templates. use when you need to list all templates for the authenticated user.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Register User
Tool to register a new user account. use after collecting valid user credentials.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Retrieve Template by ID
Tool to retrieve a template by id. use when you have a valid template id and need full template details. use after confirming this detail.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub and Supportivekoala, 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 Supportivekoala.