Create Writer summaries for GitHub README changes
Keep documentation changes visible without asking everyone to spot them in a commit history.
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
Text Generation
Tool to generate text based on a given prompt. use when you need model-driven completions after crafting a prompt.
Why this helps
Important setup or product guidance can change quietly in a README and get overlooked by the people who need it.
- Improves documentation awareness
- Makes contributor updates easier
Setup
Build it in a few focused steps.
- 1Connect GitHub and Writer to Notis once.
- 2Create an automation in the portal or describe it to Notis.
- 3Ask for a team-facing summary when the repository README changes.
- 4Pick the README change trigger and a run-report channel.
- 5Edit a test README to confirm the summary.
Questions about this workflow
Can this watch a README in a subdirectory?
The GitHub trigger can monitor a configurable repository directory.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Writer. A trigger fires from one place; an action lands in another.
GitHub triggers
Writer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Ask Question to Knowledge Graph
Tool to send a question to the knowledge graph and retrieve the answer. use after defining your question and optional context.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Chat Completion
Tool to generate chat-based completions. use when you need conversational ai responses; call after assembling system and user messages.
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.
Create Knowledge Graph
Tool to create a new knowledge graph. use after defining nodes and edges to persist the graph.
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.
Delete Graph
Tool to delete a knowledge graph by its id. use when you need to remove a graph after confirming its identifier.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Applications
Tool to list all no-code agent applications. use when you need to retrieve all registered applications.
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.
List Files
Tool to list all uploaded files. use when you need to retrieve a paginated set of user files, optionally filtered by status, graph, or type. use after uploading files to inspect available files.
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.
List Knowledge Graphs
Tool to retrieve a list of knowledge graphs. use when you need an overview of existing graphs.
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.
List Models
Tool to list all available language models. use when you need to discover which models can be used for completions.
Connect any two apps with Notis in the middle.
GitHub and Writer, 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 Writer.