Keep release context current as details change
When release notes or publication status shifts, see whether the surrounding story has shifted too.
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
Get Stories
Tool to retrieve clusters of related articles covering the same event or topic with aggregate metrics. Use when you need to fetch filtered and sorted story clusters after configuring query parameters.
Why this helps
Release edits can change positioning while external coverage continues moving independently.
- Spot changing coverage themes
- Keep release positioning current
- Reduce repeated news searches
Setup
Build it in a few focused steps.
- 1Connect GitHub and Perigon to Notis once through the portal.
- 2Create the automation in Automations or ask Notis to create it.
- 3Use this instruction: “When this GitHub release changes, retrieve Perigon story clusters related to the release, product area, and named companies, then summarize any meaningful change in coverage or narrative.”
- 4Pick the release state changed trigger, choose the report channel, and test with one release update.
Questions about this workflow
What release changes can trigger it?
The GitHub event can monitor supported changes such as notes, publication state, prerelease state, or assets.
Why use story clusters?
They provide an aggregated view of related coverage and narrative movement.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Perigon. A trigger fires from one place; an action lands in another.
GitHub triggers
Perigon actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get News Articles
Tool to retrieve a list of news articles based on filters. Use when keywords, sources, or date ranges are specified.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Companies
Tool to retrieve information on companies in Perigon’s entity database. Use when you need a full list of companies. Use after confirming a valid API key is present.
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.
Get Journalists
Tool to retrieve journalist profiles including title, Twitter handle, bio, and location. Use when you need detailed journalist info to enrich content with author metadata.
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.
Get Media Sources
Tool to retrieve a list of media sources with filtering options. Use when you need to list sources by domain, country, category, or traffic metrics.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Stories
Tool to retrieve clusters of related articles covering the same event or topic with aggregate metrics. Use when you need to fetch filtered and sorted story clusters after configuring query parameters.
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.
Get Topics
Tool to retrieve all available Perigon news topics. Returns a list of topics that can be used to filter articles or stories. Each topic includes an ID, name, and labels (category/subcategory).
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.
Get Wikipedia Articles
Tool to search and filter Wikipedia pages. Use when you have a search query ready and want to retrieve relevant Wikipedia articles.
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.
Vector Search Articles
Tool to perform a vector search on Perigon’s real-time news database. Use when you need to retrieve semantically similar news articles given a natural language query.
Connect any two apps with Notis in the middle.
GitHub and Perigon, 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 Perigon.