Bring campaign analysis into release follow-up
A release detail changed. Prompt a campaign analysis download so release follow-up can include the campaign's available findings.
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
Download Campaign PDF Analysis
Tool to download a pdf analysis report for a processed campaign. use after a campaign has been processed.
Why this helps
Campaign analysis can be overlooked during release work when campaign reporting sits outside the code team's routine.
- Connects release changes with a campaign analysis follow-up.
- Makes available campaign findings easier to include in release review.
- Cuts down on separate manual checks across tools.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Campaign cleaner once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for release analysis follow-up.
- 3Describe in one instruction which processed campaign to use and how to report the available PDF analysis.
- 4Choose the GitHub Release State Changed trigger and select where run reports should go.
- 5Test with one real release change and confirm the report explains whether analysis was available.
Questions about this workflow
Will this work for a campaign that has not been processed?
The PDF analysis action is intended for a processed campaign. The workflow should report clearly if analysis is not available.
Can the trigger cover any release?
The listed trigger monitors a specific GitHub release by tag name. Configure it for the release you want monitored.
Does the action send the PDF to someone?
The available action downloads the PDF analysis. Choose a Notis report destination to receive the run report; delivery behavior for the file depends on the connected action's result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Campaign cleaner. A trigger fires from one place; an action lands in another.
GitHub triggers
Campaign cleaner actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Campaign
Tool to delete a saved campaign by id. use when you need to remove a campaign after confirming its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Campaign List
Tool to list all campaigns in the account. use when you need to retrieve campaign listings for reporting or management.
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.
Download Campaign PDF Analysis
Tool to download a pdf analysis report for a processed campaign. use after a campaign has been processed.
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 Campaign Status
Tool to check the processing status of a submitted campaign. use after submitting a campaign to monitor its progress.
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 Campaign cleaner, 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 Campaign cleaner.