Inspect deployment details after a code-scanning alert
Give security findings immediate deployment context without a separate investigation task.
Trigger
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.
Action
Get deployment details
Tool to retrieve detailed information about a specific deployment. use after triggering a deployment and you need to inspect its status and configuration. example: "get details for deployment dpl 123abc".
Why this helps
It takes extra mental effort to connect a new code alert with the deployment that may need review.
- Keeps response context together
- Supports calmer incident triage
- Reduces lookup work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Vercel through Notis once.
- 2Create a new automation in the portal.
- 3Write a prompt to get the relevant Vercel deployment details after a code-scanning alert, select the alert trigger, choose reports, and test with an example alert.
Questions about this workflow
Is this a deployment action?
No. It retrieves deployment details to support investigation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Vercel. A trigger fires from one place; an action lands in another.
GitHub triggers
Vercel 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 Environment Variable
Tool to add an environment variable to a vercel project. use after confirming the project exists and you need to configure secrets or configuration values across environments before deployment. example: "add api key=secret to production".
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.
Check Cache Artifact Exists
Tool to check if a cache artifact exists by its hash. use when verifying whether a cache artifact is already stored before upload.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Domain Availability
Tool to check if a domain is available for registration. use when you need to verify domain availability before purchase.
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 Domain Price
Tool to check the price for a domain before purchase. use when evaluating cost and availability prior to domain registration.
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.
Create Auth Token
Tool to create a new authentication token. use when you need to programmatically generate a new token after validating permissions. example: "create auth token named my-token"
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 Edge Config
Tool to create a new edge config for a vercel project. use when you need to define edge caching settings before deploying your project across a specified repository.
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.
Create Edge Config Token
Tool to create a new token for a specific edge config. use when you need a read-only access token after provisioning your edge config.
Commit Event
Triggered when a new commit is pushed to a repository.
Create new deployment
Tool to create a new deployment. use when you need to deploy files or a git commit to a vercel project.
Connect any two apps with Notis in the middle.
Not just GitHub and Vercel. 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 Vercel.