Make email blockers visible as ClickUp dependencies
Connect the blocked work to what it is waiting on, so dependencies are easier to follow.
Trigger
New Email Received
Trigger for new emails in an AgentMail inbox
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 dependency mentioned in email can disappear from view once people return to their task lists.
- Record clear blockers in the task relationship itself.
- Make waiting work easier to recognize in ClickUp.
- Keep the email explanation available in the workflow report.
Setup
Build it in a few focused steps.
- 1Connect Agent Mail and ClickUp once in the Notis portal.
- 2Create an automation in Automations, then choose a name and report channel.
- 3Tell Notis to add a ClickUp dependency only when a new email clearly identifies both the blocked task and the prerequisite task, using the correct dependency direction.
- 4Pick the Agent Mail New Email Received trigger and choose where run reports go.
- 5Test with one real blocker email and check the dependency direction.
Questions about this workflow
What if the email does not identify both tasks?
Ask Notis to skip creating a dependency unless it can identify both tasks reliably.
Can one task both wait on and block another in the same action?
The action requires one dependency direction at a time. Instruct Notis to choose the direction supported by the message.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agent mail to Clickup. A trigger fires from one place; an action lands in another.
Agent mail 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 Email Received
Trigger for new emails in an AgentMail inbox
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.
Agent mail 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.