Connect documentation changes to communication
A README update can change how people use your product; give it the right visibility.
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
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
Why this helps
Documentation improvements often ship quietly even when they change onboarding, setup, or product understanding.
- Improves documentation visibility
- Supports better onboarding
- Reduces duplicate update announcements
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mailsoftly once in Notis.
- 2Create the automation in the portal or ask Notis to authenticate Mailsoftly and prepare an update only when a README change is meaningful to users or contributors.
- 3Select GitHub Repository README Changed and choose a reporting channel.
- 4Test with one documentation change.
Questions about this workflow
Can minor edits be ignored?
Yes. Tell Notis to focus on setup, onboarding, API, or breaking documentation changes.
Can this create a draft instead of sending?
Yes. Request a draft or review-ready summary in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mailsoftly. A trigger fires from one place; an action lands in another.
GitHub triggers
Mailsoftly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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.
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 Mailsoftly, 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 Mailsoftly.