Keep compliance task order clear
Make prerequisite work visible in ClickUp as 21risk follow-ups are reviewed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
A dependent remediation task can appear ready even when another compliance action must happen first.
- Show prerequisite relationships in ClickUp.
- Help teammates understand what can start now.
- Reduce stalled work caused by hidden dependencies.
Setup
Build it in a few focused steps.
- 1Connect 21risk and ClickUp once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to review the supplied 21risk follow-ups and add a ClickUp waiting-on or blocking dependency where the prerequisite is clear.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real prerequisite and accessible ClickUp tasks.
Questions about this workflow
Can the automation add both dependency directions in one action?
No. Each run must specify either depends on or dependency of.
What if the review does not identify a clear prerequisite?
The instruction should have Notis skip adding a dependency when the relationship is not supported by the available information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Clickup. A trigger fires from one place; an action lands in another.
21risk 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.
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.
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.
Add tags from time entries
Associates a list of specified tags with one or more time entries within a given team (workspace).
Add tag to task
Adds an existing tag to a specified task; team id is required if custom task ids is true.
Add task link
Links two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).
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.
21risk 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.