

How to Set Up Priority Escalation Alerts with Power Automate
Automatically sends Slack DMs to assignees and their managers when ClickUp task priority changes to Urgent.
Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Best for
Teams that need instant notification when critical tasks emerge and want to notify both doers and decision-makers.
Not ideal for
Teams that prefer channel-based notifications over direct messages or don't have clear manager hierarchies.
Sync type
real-timeUse case type
notificationReal-World Example
A 25-person product team uses this to alert both the developer and their team lead when a bug gets escalated to Urgent priority. Before automation, urgent tasks sat unnoticed for hours because people don't constantly check ClickUp. Now the right people know within 30 seconds.
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.





Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
Implementation
Import this workflow directly into Power Automate
Copy the pre-built Power Automate blueprint and paste it straight into Power Automate. All modules, filters, and field mappings are already configured — you just need to connect your accounts.
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Task Name | ||
| Task URL | ||
| Assignee Username | ||
| Priority Level | ||
4 optional fields▸ show
| Due Date | |
| Project Name | |
| Task Description | |
| Changed By |
Step-by-Step Setup
My flows > + New flow > Automated cloud flow
Create new automated flow
Navigate to make.powerautomate.com and sign in with your Microsoft account. Click 'My flows' in the left sidebar, then the '+ New flow' button. Select 'Automated cloud flow' from the dropdown menu. Name your flow 'ClickUp Priority Escalation' and leave the trigger blank for now.
- 1Click 'My flows' in the left navigation
- 2Click '+ New flow' button
- 3Select 'Automated cloud flow'
- 4Enter flow name: 'ClickUp Priority Escalation'
- 5Click 'Skip' to choose trigger later
Flow designer > Choose trigger > HTTP
Add ClickUp webhook trigger
Click on the trigger step and search for 'HTTP' in the connector search. Select 'When a HTTP request is received' trigger. Power Automate will generate a webhook URL automatically. Copy this URL - you'll need it in ClickUp. Click 'Use sample payload to generate schema' and we'll configure the JSON schema next.
- 1Click on the empty trigger step
- 2Search for 'HTTP' in the connector list
- 3Select 'When a HTTP request is received'
- 4Copy the generated HTTP POST URL
- 5Click 'Use sample payload to generate schema'
HTTP trigger > Use sample payload to generate schema
Configure ClickUp webhook payload schema
Paste this JSON schema into the sample payload box to define what ClickUp will send. This tells Power Automate the structure of incoming webhooks when task priorities change. The schema includes task details, assignee info, and the priority change that triggered the webhook.
- 1Paste the ClickUp webhook schema into the text box
- 2Click 'Done' to generate the schema
- 3Verify the schema fields appear in the dynamic content
Flow designer > + New step > Control > Condition
Add priority filter condition
Click '+ New step' and search for 'Condition' in the actions. Add a condition to only proceed when priority equals 'urgent'. Set the left value to 'priority' from dynamic content, choose 'is equal to' as the operator, and enter 'urgent' as the right value. This prevents notifications for non-urgent priority changes.
- 1Click '+ New step' below the trigger
- 2Search for and select 'Condition'
- 3Click the left value box and select 'priority' from dynamic content
- 4Set operator to 'is equal to'
- 5Type 'urgent' in the right value box
Condition > If yes > Add an action > Slack
Set up Slack connection
In the 'If yes' branch, click 'Add an action' and search for 'Slack'. Select the Slack connector, then choose 'Post message' action. Power Automate will prompt you to sign in to Slack. Authorize the connection with a Slack admin account that has permission to send DMs to all team members.
- 1Click 'Add an action' in the 'If yes' branch
- 2Search for and select 'Slack'
- 3Choose 'Post message' from the actions list
- 4Click 'Sign in' when prompted
- 5Authorize Power Automate in your Slack workspace
Slack > Post message > Message configuration
Configure assignee DM
Set the 'Post as' field to 'Power Automate' and 'Post in' to 'Direct message'. For the recipient, you'll need to map ClickUp usernames to Slack user IDs. In the message text, create an urgent task alert that includes the task name, URL, and context about the priority escalation. Use dynamic content to pull task details from the webhook.
- 1Set 'Post as' to 'Power Automate'
- 2Set 'Post in' to 'Direct message'
- 3Configure recipient user mapping
- 4Enter urgent task message template
- 5Add task name and URL from dynamic content
If yes branch > Add an action > Slack > Post message
Add manager notification
Click 'Add an action' below the assignee DM to create a second Slack message for the manager. Use another 'Post message' action with similar settings but different recipient mapping. Include context that this is a manager notification about their team member's urgent task. You'll need a separate lookup to map assignees to their managers' Slack IDs.
- 1Click 'Add an action' below the first Slack message
- 2Select Slack > Post message again
- 3Configure manager recipient mapping
- 4Create manager notification message template
- 5Include assignee name and task context
ClickUp Space > Settings > Integrations > Webhooks
Set up ClickUp webhook endpoint
Copy your Power Automate webhook URL and head to ClickUp. Go to your Space settings, click 'Integrations', then 'Webhooks'. Create a new webhook pointing to your Power Automate URL. Set it to trigger on 'Task Updated' events and filter for priority changes only. Test the webhook with a sample task.
- 1Open ClickUp and navigate to Space settings
- 2Click 'Integrations' then 'Webhooks'
- 3Click '+ New Webhook'
- 4Paste your Power Automate webhook URL
- 5Select 'Task Updated' as the trigger event
- 6Save and test the webhook
ClickUp task > Priority dropdown > Urgent
Test with real priority change
Create a test task in ClickUp and change its priority to Urgent. Check your Power Automate run history to see if the flow triggered correctly. Verify that both the assignee and manager received Slack DMs with the correct task information. Fix any field mapping issues or user lookup problems you discover.
- 1Create a test task in ClickUp
- 2Assign it to yourself
- 3Change priority from Normal to Urgent
- 4Check Power Automate run history
- 5Verify Slack DMs were sent correctly
Flow designer > Turn on toggle
Enable and monitor
Turn on your flow by clicking the toggle switch in the top right. Monitor the first few real escalations carefully to catch any edge cases. Set up email notifications for flow failures so you know when urgent escalations aren't reaching their targets. Document the user mapping logic for future team member changes.
- 1Click the 'Turn on' toggle in the top right
- 2Enable email notifications for failures
- 3Document user mapping process
- 4Monitor first few real escalations
- 5Update team documentation
Use Parse JSON with a lookup table to handle user mapping between ClickUp usernames and Slack user IDs. This expression handles missing mappings gracefully.
JavaScript — Code Step{▸ Show code
{
"type": "object",
"properties": {... expand to see full code
{
"type": "object",
"properties": {
"userMappings": {
"sarah.chen": "U024BE7LH",
"mike.torres": "U024BE8MJ",
"alex.kim": "U024BE9NK"
},
"managerMappings": {
"sarah.chen": "mike.torres",
"alex.kim": "mike.torres"
}
}
}
@{if(contains(outputs('Parse_JSON')?['body']?['userMappings'], triggerBody()?['assignee']), outputs('Parse_JSON')?['body']?['userMappings'][triggerBody()?['assignee']], 'U024FALLBACK')}
@{if(contains(outputs('Parse_JSON')?['body']?['managerMappings'], triggerBody()?['assignee']), outputs('Parse_JSON')?['body']?['userMappings'][outputs('Parse_JSON')?['body']?['managerMappings'][triggerBody()?['assignee']]], null)}Going live
Production Checklist
Before you turn this on for real, confirm each item.
Troubleshooting
Common errors and how to fix them.
Frequently Asked Questions
Common questions about this workflow.
Analysis
Use Microsoft Power Automate for this if your team already lives in the Microsoft ecosystem and you need reliable webhook handling without coding. Power Automate's HTTP trigger is rock-solid and the Slack connector handles DM permissions better than most platforms. The built-in error handling and retry logic works well for mission-critical notifications. Pick n8n instead if you need complex user mapping logic or want to avoid Microsoft's per-user licensing.
This costs around $15/month per user with Power Automate Premium, but most teams already have this through Microsoft 365 Business Premium. Each priority escalation uses 2-3 actions (condition + two Slack messages), so 100 escalations monthly barely dents your quota. Zapier would cost $20/month for the same volume and lacks webhook reliability. Make is cheaper at $9/month but their Slack connector has more DM permission issues.
Make handles user mapping better with its iterator and lookup functions - you can build complex org charts without Parse JSON gymnastics. Zapier's Formatter helps with text manipulation if you want fancier notification templates. n8n gives you real database lookups for user hierarchies instead of hard-coded JSON. Pipedream's async handling prevents webhook timeouts with large team notifications. But Power Automate wins on enterprise reliability and integration depth with Microsoft tools your team probably already uses.
You'll hit webhook payload changes when ClickUp updates their API - suddenly your JSON schema breaks and notifications stop. Slack user IDs are permanent but usernames change, so map by ID not display name. ClickUp's webhook retry logic is aggressive and will hammer your endpoint if it returns errors, potentially triggering duplicate notifications hours apart. The biggest gotcha: assignees in ClickUp can be multiple people, but your logic probably assumes single assignment.
Ideas for what to build next
- →Add escalation delays — Create a second flow that sends follow-up messages if urgent tasks remain incomplete after 1 hour.
- →Include task context — Enhance notifications with task description, comments, and custom field data for richer context.
- →Build completion alerts — Send confirmation DMs when urgent tasks are marked complete to close the feedback loop.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup