Keep onboarding emails aligned with your README
Update your documentation once and keep the onboarding message useful.
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
Update Template
Tool to update an existing template's name or content. use when you need to modify a template's html or structured html by its uuid.
Why this helps
Documentation and onboarding emails drift apart, creating avoidable confusion and repeated explanations.
- Reduces conflicting instructions
- Lowers repetitive support questions
- Keeps onboarding closer to the source of truth
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mailcoach to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Tell Notis: When the onboarding README changes, update the matching Mailcoach onboarding template with the current instructions.
- 4Pick the README changed trigger, choose a reporting channel, and test with one documentation update.
Questions about this workflow
Can this watch a README in a specific branch?
Yes. Include the repository path and branch in the automation instruction.
Can Notis preserve the template design?
Ask it to update the content while preserving the existing Mailcoach template structure.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mailcoach. A trigger fires from one place; an action lands in another.
GitHub triggers
Mailcoach actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Mailcoach Campaign
Tool to create a new mailcoach campaign. use when you need to send or schedule an email campaign to a specific list or segment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Email List
Tool to create a new email list. use when you need to manage and organize subscribers before sending campaigns. use 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.
Add suppression
Tool to add a suppression entry. use after detecting a bounce, spam complaint, or manual block.
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.
Add Tag to Email List
Tool to create a new tag within a specific email list. use after confirming the email list exists.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add Tags to Subscriber
Tool to add tags to a subscriber. use after retrieving a subscriber's uuid to segment them.
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.
Add Template
Tool to create a new email template. use after preparing template name and optional html content.
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.
Add Transactional Email Template
Tool to create a new template that can be used for transactional emails.
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.
Append to Subscriber Import
Tool to append csv data to an existing subscriber import. use after retrieving a subscriber import when additional subscriber data needs to be added.
Connect any two apps with Notis in the middle.
GitHub and Mailcoach, 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 Mailcoach.