Skip to content
Notis

Find the right response decision when a secret is detected

Sensitive alerts demand a fast path to the decisions that govern response.

Trigger

New Secret Scanning Alert Detected

Triggers when a new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filtering by secret type (e.g., personal access tokens, AWS keys) and by token validity status (active, inactive, unknown). The payload includes the alert number, secret type, validity status, resolution state, timestamps, URLs, and flags for push protection bypass, public exposure, and multi-repo detection.

Action

List Polls

Tool to list all polls accessible to the user. use when you need to retrieve poll ids and basic metadata.

Why this helps

Founders may waste precious time searching for incident or credential-rotation context.

  • Surfaces prior response decisions quickly.
  • Reduces duplicated incident coordination.
  • Helps keep sensitive follow-up focused.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Loomio to Notis once through the portal.
  • 2Create an automation or ask Notis to list relevant Loomio polls when a new secret scanning alert is detected.
  • 3Use the instruction: identify accessible polls about exposure response, credential rotation, notification, or incident handling and report only relevant details.
  • 4Pick the new secret scanning alert trigger and choose a secure reporting channel.
  • 5Test it with a non-sensitive test alert if possible.

Questions about this workflow

Will the secret value appear in the report?

The instruction should explicitly request that secret values never be repeated, and Notis should report only safe metadata.

Can this focus on active secrets?

Yes. Ask Notis to prioritize alerts with active or unknown validity status.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Loomio. A trigger fires from one place; an action lands in another.

GitHub triggers

Loomio actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

List Groups

Tool to list all groups accessible to the user. use when you need to retrieve and paginate user groups.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List Polls

Tool to list all polls accessible to the user. use when you need to retrieve poll ids and basic metadata.

ActionInstant

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.

TriggerPolling

Show Group

Tool to retrieve details of a specific group. use when you have a group id and need its full metadata.

ActionInstant

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.

TriggerPolling

SHOW_POLL

Tool to retrieve details of a specific poll. use when you have a poll id and need its full metadata.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

Connect any two apps with Notis in the middle.

GitHub and Loomio, 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 Loomio.