Keep release communication aligned with the latest details
When the release changes, the explanation should have an easy way to change with it.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
List templates
This tool retrieves a list of all available templates in the echtpost account. templates serve as the base design for postcards and are essential for creating cards. the action operates independently using only an authentication token and returns detailed template information including id, name, description, preview url, type, and creation time. this action is crucial for viewing templates before creating cards and obtaining the necessary template ids for subsequent actions.
Why this helps
Release notes evolve, but communication drafts and plans often remain based on outdated details.
- Reduces stale release communication
- Creates a prompt to revisit audience and tone
- Makes changing launch plans easier to manage
Setup
Build it in a few focused steps.
- 1Connect GitHub and Echtpost to Notis once through the portal.
- 2Create a new automation in the portal or describe it to Notis in plain language.
- 3Use this instruction: When a GitHub release changes, list Echtpost templates that fit the updated release context and explain what kind of audience each supports.
- 4Select the release state changed trigger, choose the run-report channel, and test with one edited release.
Questions about this workflow
Can it run only when release notes change?
Yes. State that Notis should focus on changes to the release body or notes.
Will it update an existing Echtpost message?
No. The available action retrieves templates for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Echtpost. A trigger fires from one place; an action lands in another.
GitHub triggers
Echtpost actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List templates
This tool retrieves a list of all available templates in the echtpost account. templates serve as the base design for postcards and are essential for creating cards. the action operates independently using only an authentication token and returns detailed template information including id, name, description, preview url, type, and creation time. this action is crucial for viewing templates before creating cards and obtaining the necessary template ids for subsequent actions.
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 Echtpost, 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 Echtpost.