Turn recurring 21risk requirements into task steps
Bring current audit requirements into a checklist the task owner can work through.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create checklist
Creates a new checklist with a specified name within an existing task, which can be identified by its standard id or a custom task id (if `custom task ids` is true, `team id` is also required).
Why this helps
Recurring requirements can be hard to act on when they remain in compliance records instead of the task itself.
- Make scheduled review requirements actionable.
- Keep compliance steps attached to the task they support.
- Reduce manual checklist setup after recurring reviews.
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 current 21risk requirements and create a checklist on the specified ClickUp task when follow-up is needed.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real review and an existing task.
Questions about this workflow
Will this update or replace an existing checklist?
This action creates a checklist. The instruction should avoid repeated creation unless a new checklist is intended for each run.
How does the task get identified?
Specify the ClickUp task in your instruction or provide its identifying context to the automation.
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.