Intermediate~15 min setupProject Management & CommunicationVerified April 2026
ClickUp logo
Slack logo

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-time

Use case type

notification

Real-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.

/mo
505005K50K

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

Skip the setup

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.

ClickUp admin access to create webhooks in your Space
Slack admin permissions to authorize workspace integrations
Microsoft Power Automate license (included with most Microsoft 365 plans)
Mapping of ClickUp usernames to Slack user IDs for your team
Manager hierarchy mapping to know who to notify for each assignee

Field Mapping

Map these fields between your apps.

FieldAPI 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

1

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.

  1. 1Click 'My flows' in the left navigation
  2. 2Click '+ New flow' button
  3. 3Select 'Automated cloud flow'
  4. 4Enter flow name: 'ClickUp Priority Escalation'
  5. 5Click 'Skip' to choose trigger later
What you should see: You should see the flow designer with an empty trigger step at the top.
2

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.

  1. 1Click on the empty trigger step
  2. 2Search for 'HTTP' in the connector list
  3. 3Select 'When a HTTP request is received'
  4. 4Copy the generated HTTP POST URL
  5. 5Click 'Use sample payload to generate schema'
What you should see: You should see a webhook URL starting with https://prod-XX.eastus.logic.azure.com and a schema input box.
Common mistake — Don't share this webhook URL publicly - anyone with it can trigger your flow and potentially spam your Slack.
Power Automate
+
click +
search apps
ClickUp
CL
ClickUp
Add ClickUp webhook trigger
ClickUp
CL
module added
3

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.

  1. 1Paste the ClickUp webhook schema into the text box
  2. 2Click 'Done' to generate the schema
  3. 3Verify the schema fields appear in the dynamic content
What you should see: Power Automate should show parsed fields like task_id, name, assignees, priority, and url in the dynamic content picker.
Common mistake — ClickUp's webhook payloads vary by event type - this schema only works for task update webhooks, not task creation.
4

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.

  1. 1Click '+ New step' below the trigger
  2. 2Search for and select 'Condition'
  3. 3Click the left value box and select 'priority' from dynamic content
  4. 4Set operator to 'is equal to'
  5. 5Type 'urgent' in the right value box
What you should see: You should see a condition with two branches: 'If yes' and 'If no'. We'll build our alerts in the 'If yes' branch.
Common mistake — ClickUp priority values are lowercase ('urgent', not 'Urgent') - mismatched casing will cause the condition to always fail.
ClickUp
CL
trigger
filter
Priority
matches criteria?
yes — passes through
no — skipped
Slack
SL
notified
5

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.

  1. 1Click 'Add an action' in the 'If yes' branch
  2. 2Search for and select 'Slack'
  3. 3Choose 'Post message' from the actions list
  4. 4Click 'Sign in' when prompted
  5. 5Authorize Power Automate in your Slack workspace
What you should see: You should see 'Connected' status next to Slack and be able to select channels/users in the message configuration.
Common mistake — The Slack user who authorizes this connection needs permission to DM all team members - standard member accounts often can't DM everyone.
6

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.

  1. 1Set 'Post as' to 'Power Automate'
  2. 2Set 'Post in' to 'Direct message'
  3. 3Configure recipient user mapping
  4. 4Enter urgent task message template
  5. 5Add task name and URL from dynamic content
What you should see: The message preview should show urgent task details with ClickUp data populated from the webhook payload.
Common mistake — ClickUp provides usernames, but Slack needs user IDs - you'll need a lookup table or Parse JSON to convert between them.
7

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.

  1. 1Click 'Add an action' below the first Slack message
  2. 2Select Slack > Post message again
  3. 3Configure manager recipient mapping
  4. 4Create manager notification message template
  5. 5Include assignee name and task context
What you should see: You should have two Slack message actions in sequence, one for assignee and one for manager.
Common mistake — Manager lookups often fail if team structure changes - build in error handling or default to a team channel.
8

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.

  1. 1Open ClickUp and navigate to Space settings
  2. 2Click 'Integrations' then 'Webhooks'
  3. 3Click '+ New Webhook'
  4. 4Paste your Power Automate webhook URL
  5. 5Select 'Task Updated' as the trigger event
  6. 6Save and test the webhook
What you should see: ClickUp should show a successful webhook test, and you should see a test run appear in Power Automate's run history.
Common mistake — ClickUp webhooks fire for ALL task updates by default - make sure to enable filtering or your flow will trigger constantly.
9

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.

  1. 1Create a test task in ClickUp
  2. 2Assign it to yourself
  3. 3Change priority from Normal to Urgent
  4. 4Check Power Automate run history
  5. 5Verify Slack DMs were sent correctly
What you should see: You should receive a Slack DM about the urgent task, and the flow run should show green success checkmarks.
Common mistake — If your test fails, check that the ClickUp user assigned to the task has a corresponding Slack user mapping in your lookup logic.
Power Automate
▶ Test flow
executed
ClickUp
Slack
Slack
🔔 notification
received
10

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.

  1. 1Click the 'Turn on' toggle in the top right
  2. 2Enable email notifications for failures
  3. 3Document user mapping process
  4. 4Monitor first few real escalations
  5. 5Update team documentation
What you should see: The flow status should show 'On' and begin processing real priority escalations from ClickUp.

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

VerdictWhy n8n for this workflow

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.

Cost

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.

Tradeoffs

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 delaysCreate a second flow that sends follow-up messages if urgent tasks remain incomplete after 1 hour.
  • Include task contextEnhance notifications with task description, comments, and custom field data for richer context.
  • Build completion alertsSend confirmation DMs when urgent tasks are marked complete to close the feedback loop.

Related guides

Was this guide helpful?
ClickUp + Slack overviewPower Automate profile →