Keep release context available after launch day
Release knowledge should remain useful after the announcement fades.
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
Store Data in Dataset
Tool to store data items in a dataset. use after collecting data when you want to batch-append or update items in an existing dataset.
Why this helps
Release notes, supporting evidence, and launch context are easy to lose once the immediate launch work is over.
- Creates a durable release record
- Supports future launch retrospectives
- Reduces repeated historical research
Setup
Build it in a few focused steps.
- 1Connect GitHub and Apify once in Notis.
- 2Create the automation with an instruction to store the changed release details and any requested supporting research in an Apify dataset.
- 3Choose GitHub Release State Changed as the trigger.
- 4Select a reporting channel and test by updating a draft release.
Questions about this workflow
Can this track published releases only?
Tell Notis to focus on publication changes or a specified release state.
Can the dataset be reused later?
Yes. The stored records can support later research or reporting workflows.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Apify. A trigger fires from one place; an action lands in another.
GitHub triggers
Apify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Actor
Tool to create a new actor with specified configuration. use when you need to initialize a fresh actor programmatically before publishing or running it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Dataset
Tool to create a new dataset. use when you need to initialize or retrieve a dataset by name.
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 Actor Task
Tool to create a new actor task with specified settings. use when you need to configure or schedule recurring actor runs programmatically.
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.
Create Task Webhook
Tool to create a webhook for an actor task. use when you need external notifications about task run events (e.g., completion or failure) in downstream systems.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Actor
Tool to delete an actor permanently. use when you need to remove an actor by its id or username~actorname. confirm before calling.
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.
Delete Webhook
Tool to delete a webhook by its id. use when removing a webhook after confirming the webhook id.
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 Actor Details
Tool to get details of a specific actor. use when you need actor metadata by id or username/actorname.
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.
Get all webhooks
Tool to get a list of all webhooks created by the user. use when you need to enumerate webhooks before filtering or maintenance.
Connect any two apps with Notis in the middle.
GitHub and Apify, 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 Apify.