Keep changing priorities connected to content
When an issue changes direction, the content around it may need to change too.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
List Document Exports
Tool to retrieve a paginated list of document exports. use after initiating export jobs to fetch export history.
Why this helps
State, ownership, or scope changes can leave outdated guides and announcements unnoticed.
- Create a dependable review point for meaningful issue changes.
- Highlight when content may no longer match the work.
- Reduce stale documentation and forgotten follow-up.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cloudpress to Notis once through the portal.
- 2Create an automation or ask Notis to review Cloudpress exports when tracked GitHub issue properties change and flag possible content follow-up.
- 3Pick the issue properties trigger and the channel for run reports.
- 4Test with one real issue update.
Questions about this workflow
Which issue changes can start it?
The GitHub trigger covers tracked properties such as state, title, body, assignees, labels, and milestone.
Can it avoid noisy updates?
Ask Notis to report only changes that suggest documentation or communication impact.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Cloudpress. A trigger fires from one place; an action lands in another.
GitHub triggers
Cloudpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Information
Tool to retrieve authenticated account information. use after authentication to get current account details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Connections
Tool to list all connections with pagination. use when you need to retrieve cloudpress connections page by page with optional filters like kind, type, or sourcereference.
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.
List Document Exports
Tool to retrieve a paginated list of document exports. use after initiating export jobs to fetch export history.
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.
List Webhooks
Tool to retrieve a paginated list of webhooks. use when you need an overview of all configured webhooks.
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 Cloudpress, 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 Cloudpress.