Turn code scanning alerts into owned work
Give security findings a clear place, context, and next step.
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
Create a task
Creates a new clickup task in a specific list, optionally as a subtask if a `parent` task id (which cannot be a subtask itself and must be in the same list) is provided.
Why this helps
Security alerts can remain unresolved because they compete with feature work for attention.
- Creates an actionable record for each finding
- Preserves severity and affected location
- Makes security follow-up easier to prioritize
Setup
Build it in a few focused steps.
- 1Connect GitHub and ClickUp to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for it in plain language.
- 3Use this instruction: When a new GitHub code scanning alert is created, create a ClickUp remediation task with the rule, severity, affected location, tool, alert number, and link.
- 4Pick the code scanning alert trigger, choose a reporting channel, and test with one real alert.
Questions about this workflow
What alert details are useful in ClickUp?
The rule, severity, scanning tool, affected location, alert number, and direct link provide useful starting context.
Does this replace GitHub security tooling?
No. It adds an operational follow-up task while GitHub remains the source of the alert.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Clickup. A trigger fires from one place; an action lands in another.
GitHub triggers
Clickup 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 dependency
Adds a 'waiting on' or 'blocking' dependency to a task, requiring either `depends on` (task becomes waiting on) or `dependency of` (task becomes blocking), but not both; `team id` is required if `custom task ids` is true.
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 guest to folder
Adds a guest to a folder with specified permissions; requires a clickup enterprise plan.
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 guest to list
Shares a clickup list with an existing guest user, granting them specified permissions; requires the workspace to be on the clickup enterprise plan.
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.
Add guest to task
Assigns a guest to a task with specified permissions; requires clickup enterprise plan, and `team id` if `custom task ids` is true.
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.
Add tags from time entries
Associates a list of specified tags with one or more time entries within a given team (workspace).
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.
Add tag to task
Adds an existing tag to a specified task; team id is required if custom task ids is true.
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.
Add task link
Links two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).
Commit Event
Triggered when a new commit is pushed to a repository.
Add task to list
Adds an existing task to an additional clickup list; the "tasks in multiple lists" clickapp must be enabled in the workspace for this.
Connect any two apps with Notis in the middle.
Not just GitHub and Clickup. Any 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 Clickup.