Keep issue changes connected to research capacity
When an issue reopens, changes owner, or gains scope, get the capacity signal before it becomes another loose end.
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
Get Subscription Status
Tool to check the remaining subscription usage for the user.
Why this helps
Issue changes can revive work without reviving the capacity planning that should accompany it.
- Catches revived work early
- Supports cleaner issue triage
- Reduces dropped balls after scope changes
Setup
Build it in a few focused steps.
- 1Connect GitHub and Similarweb digitalrank api once in the Notis portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a GitHub issue changes tracked state or properties, check Similarweb digitalrank api subscription usage and report the capacity relevant to the updated work.
- 4Pick the issue-properties trigger, choose the run-report channel, and test with one real issue change.
Questions about this workflow
Which issue changes are covered?
The event can monitor state, title, body, assignees, labels, milestone, lock status, comments, and related properties.
Is this useful for reopened issues?
Yes. A reopened issue can prompt a fresh capacity check before work resumes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Similarweb digitalrank api. A trigger fires from one place; an action lands in another.
GitHub triggers
Similarweb digitalrank api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Subscription Status
Tool to check the remaining subscription usage for the user.
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.
Not just GitHub and Similarweb digitalrank api. Any 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 Similarweb digitalrank api.