Start an impact review when GitHub detects a secret
A secret alert deserves focused follow-up. Retrieve the customer records you request and make clear that identifying affected customers requires additional information.
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 DPD Customers
Tool to list customers in your dpd account. use when you need a filtered or paginated list of customers for reporting or synchronization.
Why this helps
Security incidents can trigger scattered investigation, and a customer lookup may be mistaken for proof of who was affected.
- Start a DPD customer lookup when a new secret alert arrives.
- Keep the alert context and retrieved records together in a run report.
- Surface the limitation that the customer list does not establish exposure.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Dpd2 once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis: On a new secret scanning alert, list DPD customers and report the results with a note that the available records do not identify affected customers.
- 4Pick the GitHub New Secret Scanning Alert Detected trigger and choose where run reports go.
- 5Test with one real alert.
Questions about this workflow
Will this determine which customers were exposed?
No. The available DPD action lists customers. Determining impact requires evidence that is not provided by these actions.
Can I filter the alert first?
The GitHub trigger supports filters for secret type and token validity status. Select the supported trigger configuration you need.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Dpd2. A trigger fires from one place; an action lands in another.
GitHub triggers
Dpd2 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Storefront
Tool to retrieve details of a specific storefront by its id. use when you need storefront metadata after you have its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List DPD Customers
Tool to list customers in your dpd account. use when you need a filtered or paginated list of customers for reporting or synchronization.
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 DPD Purchases
Tool to list all purchases made through your dpd account. use when you need to retrieve purchase records with optional date filters and pagination for reporting or analysis.
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 Storefronts
Tool to list all storefronts in your dpd account. use after authenticating to fetch storefront details before managing products or purchases.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Subscribers
Tool to list subscribers for a given storefront. use when you need a paginated and filtered list of subscribers after storefront setup.
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.
DPD: Ping API
Tool to ping the api to check its status. use when verifying api connectivity before further operations.
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.
Verify DPD Notification
Tool to verify a webhook notification's authenticity by posting back the original signature and payload. use after receiving a notification to confirm it originates from dpd.
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 Dpd2, 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 Dpd2.