Make requested changes visible as a dependency
Show exactly what is waiting on code revisions.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
Action
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.
Why this helps
Requested changes can create invisible blockers across planning and delivery.
- Makes blockers explicit
- Clarifies the relationship between review and delivery
- Reduces ambiguous follow-up messages
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 to create it conversationally.
- 3Use this instruction: When a GitHub pull request review requests changes, add a ClickUp dependency so the delivery task waits on the related revision task, and include the review link.
- 4Pick the review submitted trigger, choose the run-report channel, and test with one requested-changes review.
Questions about this workflow
What does the dependency communicate?
It shows that the delivery task is waiting on revisions from the pull request review.
Can this be limited to requested changes?
Yes. State that condition in the plain-language instruction.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add guest to folder
Adds a guest to a folder with specified permissions; requires a clickup enterprise plan.
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 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.
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 task
Assigns a guest to a task with specified permissions; requires clickup enterprise plan, and `team id` if `custom task ids` is true.
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 tags from time entries
Associates a list of specified tags with one or more time entries within a given team (workspace).
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 tag to task
Adds an existing tag to a specified task; team id is required 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 task link
Links two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).
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 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.
GitHub and Clickup, 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 Clickup.