Create Immediate Tasks for Detected Secrets
A secret gets exposed in your repository. Notis creates an urgent Jira task within seconds so you can rotate credentials before they're exploited.
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
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Why this helps
Secrets are detected by GitHub scanning but go unnoticed for days or weeks. You don't find out about exposed API keys until they're already used maliciously. Manual remediation is delayed because alerts stay buried in GitHub's security tab.
- Respond to exposed secrets in minutes, not days
- Centralize security incidents in Jira
- Build accountability for credential rotation
- Prevent exploitation of exposed secrets
Setup
Build it in a few focused steps.
- 1Connect GitHub and Jira to Notis.
- 2Create an automation: 'When GitHub detects a new secret scanning alert, create a critical-priority issue in Jira immediately.'
- 3Set trigger to 'New Secret Scanning Alert Detected' and action to 'Create Issue'.
- 4Configure to include secret type, validity status, and remediation instructions in the task.
- 5Test by intentionally committing a fake secret to a test branch to trigger an alert.
Questions about this workflow
What secret types are detected?
AWS keys, GitHub tokens, Slack tokens, private keys, and many others—configure in your security settings.
What if the credential is inactive?
GitHub indicates validity. You can prioritize tasks differently for active vs. unknown credentials.
Can I auto-invalidate the secret?
GitHub's push protection can block commits. Notis creates the task; credential rotation requires manual action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Jira. A trigger fires from one place; an action lands in another.
GitHub triggers
Jira actions
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.
Add Attachment
Uploads and attaches a file to a jira issue.
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.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
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.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
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.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
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.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Link Issues
Links two jira issues using a specified link type with optional comment.
Commit Event
Triggered when a new commit is pushed to a repository.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just GitHub and Jira. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.