Make documentation changes visible
Capture the meaning of a README update before it gets lost among commits.
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
Complete Conversation
Tool to send a message to a conversation and receive the bot’s reply. use after retrieving or initiating a conversation id.
Why this helps
Important product, setup, or positioning changes can be documented in GitHub without reaching the people who need to know.
- Raises visibility for meaningful documentation changes
- Drafts clearer communication
- Reduces repeated explanation later
Setup
Build it in a few focused steps.
- 1Connect GitHub and Chatbotkit to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When the GitHub README changes, ask Chatbotkit to explain the practical meaning of the update and draft a concise internal or customer-facing note.
- 4Select the GitHub Repository README Changed trigger, choose a run-report channel, and test with one README change.
Questions about this workflow
Can it draft different audiences?
Yes. Specify whether the draft is for customers, teammates, contributors, or another audience.
Does it publish the note?
No. It prepares the communication in Chatbotkit for approval.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Chatbotkit. A trigger fires from one place; an action lands in another.
GitHub triggers
Chatbotkit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Complete Conversation
Tool to send a message to a conversation and receive the bot’s reply. use after retrieving or initiating a conversation id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Integration
Tool to create a new integration. use when you need to set up a support channel integration for a bot after collecting the integration 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.
Create Skillset
Tool to create a new skillset. use when you need to group multiple skills into a single reusable unit.
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 Bots
Tool to retrieve a paginated list of all bots. use when you need to browse or manage multiple bots, and iterate pages via cursor.
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 conversation messages
Tool to list messages in a conversation with pagination. use after obtaining a conversation id to fetch messages page by page.
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 Conversations
Tool to retrieve a paginated list of conversations. use when you need to page through conversation history.
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 Datasets
Tool to list datasets. use when you need to browse or paginate through available datasets.
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 Integrations
Tool to retrieve a list of trigger integrations. use when you need to browse or manage configured trigger integrations and iterate pages via cursor.
Connect any two apps with Notis in the middle.
GitHub and Chatbotkit, 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 Chatbotkit.