Give important documentation changes the right audience
A README change can alter how customers, contributors, or teammates understand the product.
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
List Groups
Tool to list all groups accessible to the user. use when you need to retrieve and paginate user groups.
Why this helps
Documentation updates often ship without the support or product context needed to catch downstream confusion.
- Surfaces the right review audience for documentation changes.
- Reduces missed onboarding and support implications.
- Keeps product communication aligned with repository content.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Loomio to Notis once through the portal.
- 2Create an automation or ask Notis to find relevant Loomio groups when the repository README changes.
- 3Use the instruction: identify groups that should review the documentation change for onboarding, support, contributor, or positioning impact.
- 4Pick the GitHub README changed trigger and choose a channel for run reports.
- 5Test it with one documentation update.
Questions about this workflow
Can this focus on one README directory?
Yes. The trigger can monitor a specific repository directory.
Does it create a documentation review?
No. It identifies the Loomio group where that review should happen.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Loomio. A trigger fires from one place; an action lands in another.
GitHub triggers
Loomio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Groups
Tool to list all groups accessible to the user. use when you need to retrieve and paginate user groups.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Polls
Tool to list all polls accessible to the user. use when you need to retrieve poll ids and basic metadata.
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.
Show Group
Tool to retrieve details of a specific group. use when you have a group id and need its full metadata.
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.
SHOW_POLL
Tool to retrieve details of a specific poll. use when you have a poll id and need its full metadata.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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 Loomio, 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 Loomio.