Bring delivery operations into a secret alert review
A newly detected secret may affect integrations that support operations. Use the alert as a cue to review Detrack jobs while your team investigates the security issue.
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 Jobs
Tool to list all jobs with optional filters and pagination. use when you need to retrieve jobs by date, status, country, or other criteria.
Why this helps
Security alerts can be handled in one place while operational impact is overlooked elsewhere.
- Bring delivery operations into the response to a secret alert.
- Retrieve Detrack jobs for a human-led impact review.
- Avoid assuming an alert affects deliveries when the available details do not establish a link.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Detrack once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3Tell Notis to fetch Detrack jobs after a new secret alert and summarize any operational context available, noting when impact is unknown.
- 4Pick the GitHub New Secret Scanning Alert Detected trigger and choose where run reports go.
- 5Test with one real alert and review the report for useful context.
Questions about this workflow
Does a secret alert mean Detrack is affected?
Not necessarily. The workflow retrieves jobs to support review, but the alert alone may not show whether Detrack credentials or delivery operations are involved.
Will the workflow disable anything or edit a delivery?
No. It only lists Detrack jobs. Your team handles investigation and any response.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Detrack. A trigger fires from one place; an action lands in another.
GitHub triggers
Detrack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Collection
Tool to add a new collection in detrack. use after gathering all necessary collection details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete All Collections
Tool to delete all collections in the account. use when you need to purge every collection for a specific date after confirmation.
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.
Delete All Deliveries
Tool to delete all deliveries for a specific date. use when you need to purge deliveries in bulk before scheduling new ones.
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.
Delete Delivery
Tool to delete one or more deliveries by date and d.o. number. use after confirming delivery entries to avoid accidental data loss (max 100 items per call).
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Edit Delivery
Tool to edit specific deliveries by date and d.o. number. use after confirming delivery identifiers to update their details (max 100 per call).
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.
List Jobs
Tool to list all jobs with optional filters and pagination. use when you need to retrieve jobs by date, status, country, or other criteria.
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.
Search
Tool to search for deliveries, collections, or vehicles. use after defining search criteria to retrieve matching jobs.
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.
View All Collections
Tool to view all collection jobs in detrack. use when you need to retrieve every collection job currently stored.
Connect any two apps with Notis in the middle.
GitHub and Detrack, 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 Detrack.