Make documentation changes visible
The instructions people rely on deserve the same visibility as code changes.
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 sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
Why this helps
README updates can change how the team works without reaching the people who need to adapt.
- Surfaces operational documentation changes
- Supports lightweight team communication
- Reduces stale assumptions
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mural to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create a Mural sticky note for meaningful README changes with the repository, path, summary, and link.
- 3Pick the GitHub Repository README Changed trigger.
- 4Choose a run-report channel and test with one README update.
Questions about this workflow
Can it monitor a specific branch?
Yes. Configure the README trigger for the branch or tag that matters.
Can Notis summarize the change?
Yes. Ask for a short plain-language summary suitable for the team mural.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mural. A trigger fires from one place; an action lands in another.
GitHub triggers
Mural actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get current user
Tool to retrieve information about the currently authenticated user. use when you need current user details after authentication.
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.
Get files for a mural
Tool to retrieve a list of file widgets in a mural. use after confirming the mural id when listing file attachments.
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.
Get Mural Widgets
Tool to retrieve all widgets within a specified mural. use after confirming the mural id is correct.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
MURAL Authorization Request
Tool to initiate the oauth 2.0 authorization process. use when you need to redirect a user to mural to obtain an authorization code.
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.
Not just GitHub and Mural. Any 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 Mural.