Review Ascora customer records after a GitHub secret alert
A newly detected secret can raise customer questions. Bring the current Ascora customer list into your incident review without switching tasks to fetch it manually.
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
Get Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
Why this helps
During an incident, collecting customer context from a separate system adds friction and makes follow-up easier to overlook.
- Retrieve customer records as part of secret alert triage.
- Reduce context switching during incident review.
- Get a run report with the alert and lookup outcome.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Ascora once in the Notis portal.
- 2Create an automation in the portal or from any Notis channel.
- 3Tell Notis to retrieve Ascora customers when a new GitHub secret scanning alert arrives and summarize the alert with the lookup result for review.
- 4Pick the New Secret Scanning Alert Detected trigger and choose where run reports should go.
- 5Test with one real alert or an appropriate test example.
Questions about this workflow
Will this change customer records?
No. The selected Ascora action retrieves a list of customers; it does not update customer records.
Can it determine which customer is affected?
Only if the available alert and customer data provide enough context. Ask Notis to state uncertainty rather than infer a match.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Ascora. A trigger fires from one place; an action lands in another.
GitHub triggers
Ascora actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Customer
Tool to delete a specific customer by id. use when you need to remove a customer after confirming its existence.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Quotation
Tool to create a new quotation. use when submitting a customer quote request via the ascora api.
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 Customer
Tool to delete a specific customer by id. use after confirming the customer exists.
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.
Get Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Jobs
Tool to retrieve jobs. use when you need to filter and paginate job listings from ascora.
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.
GitHub and Ascora, 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 Ascora.