Can I filter notifications by ClickUp list or assignee?

Yes, add additional conditions in your flow to check the list name or assignee fields from the webhook payload. This prevents notification overload from irrelevant projects.

What happens if Slack is down when a task changes status?

Power Automate will retry the Slack action automatically. If it continues failing, ClickUp may disable the webhook after repeated errors, so monitor your run history.

How many ClickUp spaces can use the same webhook endpoint?

Each ClickUp space needs its own webhook configured separately. You can use the same Power Automate flow for multiple spaces, but set up individual webhooks pointing to the same endpoint.

Intermediate~15 min setupProject Management & CommunicationVerified April 2026

How to Send ClickUp Task Alerts to Slack with Power Automate

Automatically posts Slack messages when ClickUp tasks change to Ready for Review or Blocked status.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Power Automate

Also on:Make Zapier N8n Pipedream

Best for

Teams that live in Slack and need immediate visibility when tasks hit review or blocking states

Not ideal for

Teams that prefer digest notifications or need complex conditional logic beyond status matching

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 12-person product team uses this to notify #dev-alerts whenever a ClickUp task moves to Ready for Review or Blocked. Before automation, developers checked ClickUp every 30 minutes and reviews sat idle for hours. Now the team sees review requests within seconds.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

cheapest

n8n

Self-Hosted plan

Power Automatethis guide

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.

Admin access to your ClickUp Space to create webhooks

Permission to install apps in your Slack workspace

Microsoft 365 account with Power Automate access

Ability to identify which ClickUp statuses trigger notifications

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Task Name		The title of the ClickUp task that changed status
New Status		The status the task changed to (Ready for Review or Blocked)
Assignee Name		Who the task is assigned to for accountability in notifications
Task URL		Direct link to the task for quick access from Slack

4 optional fields▸ show

Due Date		Task deadline to show urgency in notifications
Priority		Task priority level to help with notification urgency
Space Name		Which ClickUp space the task belongs to for context
List Name		The ClickUp list containing the task for project context

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 New flow in the top toolbar. Select Automated cloud flow from the dropdown menu. Name your flow 'ClickUp Task Status Alerts' and click Create.

1Click My flows in the left navigation
2Click New flow button
3Select Automated cloud flow
4Enter flow name 'ClickUp Task Status Alerts'
5Click Create

✓ What you should see: You should see the flow designer with an empty trigger step at the top.

Flow designer > Choose trigger > HTTP

Add HTTP webhook trigger

Click Choose your flow's trigger and search for 'HTTP'. Select 'When a HTTP request is received' trigger. This creates an endpoint that ClickUp will call when tasks change status. Leave the JSON schema blank for now - we'll configure it after setting up the ClickUp webhook.

1Click Choose your flow's trigger
2Type 'HTTP' in the search box
3Select When a HTTP request is received
4Leave Request Body JSON Schema empty
5Click New step

✓ What you should see: You should see an HTTP POST URL generated in the trigger step.

⚠

Common mistake — Don't close this tab - you'll need the webhook URL for ClickUp configuration.

Power Automate

click +

search apps

ClickUp

Add HTTP webhook trigger

ClickUp

module added

Flow designer > New step > Condition

Add condition for status filtering

Click New step and search for 'Condition'. Add a condition to filter for the two status changes we want. Set the left value to click in the dynamic content and select 'Body' from the HTTP trigger. Choose 'contains' as the operator and enter 'Ready for Review' as the value.

1Click New step
2Search for and select Condition
3Click in the left value box
4Select Body from dynamic content
5Change operator to contains
6Enter 'Ready for Review' in right value

✓ What you should see: You should see a condition box with Yes and No branches below it.

⚠

Common mistake — Use 'contains' not 'equals' because the webhook body includes more than just status.

ClickUp

trigger

filter

Status

matches criteria?

yes — passes through

no — skipped

Slack

notified

Condition > Add > Add row

Add second condition for Blocked status

In the condition settings, click Add condition to create an OR logic. Set this second condition to check if Body contains 'Blocked'. This ensures the flow triggers for both Ready for Review and Blocked status changes.

1Click Add in the condition box
2Select Add row
3Set the dropdown to Or
4Click Choose a value for the new row
5Select Body from dynamic content
6Set operator to contains and value to 'Blocked'

✓ What you should see: You should see two condition rows connected with OR logic.

⚠

Common mistake — Filters are the most common place setups break. Double-check the field name and value exactly match what your app sends — a single capital letter difference will block everything.

ClickUp > Space Settings > Integrations > Webhooks

Configure ClickUp webhook

Open ClickUp in a new tab and go to your Space settings. Click Integrations, then Webhooks, then Create Webhook. Paste the HTTP POST URL from Power Automate into the Endpoint field. Select Task Status Updated as the event type and choose the specific statuses you want to monitor.

1Open ClickUp and navigate to Space settings
2Click Integrations tab
3Click Webhooks section
4Click Create Webhook
5Paste the Power Automate URL into Endpoint
6Select Task Status Updated event

✓ What you should see: You should see a webhook created with Active status in ClickUp.

⚠

Common mistake — Webhook events are space-level, so you'll need separate webhooks for each ClickUp space.

Flow designer > HTTP trigger > Use sample payload

Test webhook and generate schema

In ClickUp, change a task to Ready for Review or Blocked status. Return to Power Automate and check the run history. Click on the successful run and copy the request body. Go back to your HTTP trigger and click Use sample payload to generate schema, then paste the copied body.

1Change a ClickUp task status to trigger the webhook
2Go to My flows > Run history in Power Automate
3Click the successful run and copy the body
4Return to flow designer
5Click Use sample payload to generate schema in HTTP trigger
6Paste the webhook body and click Done

✓ What you should see: You should see individual fields appear in the dynamic content picker instead of just 'Body'.

⚠

Common mistake — If no run appears, check that your webhook URL matches exactly and ClickUp shows the webhook as Active.

Power Automate

▶ Test flow

executed

✓

ClickUp

✓

Slack

🔔 notification

received

Condition > Yes > Add an action > Slack

Add Slack connection

In the Yes branch of your condition, click Add an action and search for 'Slack'. Select the Slack connector and choose 'Post message' action. You'll be prompted to sign in to Slack and authorize Power Automate to access your workspace.

1Click Add an action in the Yes branch
2Search for and select Slack
3Choose Post message action
4Click Sign in when prompted
5Authorize Power Automate in Slack

✓ What you should see: You should see a green connected badge next to the Slack action.

⚠

Common mistake — You need admin permissions in Slack to install the Power Automate app.

Slack action > Post message configuration

Configure Slack message

Select your target channel from the dropdown. Create a message template using dynamic content from the ClickUp webhook. Include the task name, status, assignee, and a direct link to the task. Use the task URL field from the webhook payload to create a clickable link.

1Select channel from Channel dropdown
2Click in Message text field
3Add dynamic content for task name and status
4Include assignee information
5Add task URL for direct access
6Format as: 'Task: [name] changed to [status] - [assignee] - [url]'

✓ What you should see: You should see a formatted message with dynamic ClickUp fields populated.

⚠

Common mistake — Map fields using the variable picker — don't type field names manually. Hand-typed variable names often have invisible spacing errors that produce blank output.

Slack action > Settings > Configure run after

Add error handling

Click the three dots on your Slack action and select Settings. Turn on Configure run after and select 'has failed'. Add a Compose action in the failure branch to log webhook data for debugging. This prevents lost notifications when Slack is down.

1Click three dots menu on Slack action
2Select Settings
3Toggle Configure run after
4Check 'has failed'
5Add Compose action below
6Input the full webhook body for logging

✓ What you should see: You should see a parallel path that runs only when the Slack action fails.

⚠

Common mistake — Without error handling, webhook failures can cause ClickUp to disable your endpoint after repeated failures.

Flow designer > Save

Save and test the flow

Click Save in the top toolbar to activate your flow. Test by changing a ClickUp task to Ready for Review or Blocked status. Check your Slack channel for the notification and verify all dynamic fields populate correctly. Monitor the run history for any errors.

1Click Save button in top toolbar
2Go to ClickUp and change a task status
3Check target Slack channel for message
4Verify all fields display correctly
5Check My flows > Run history for success

✓ What you should see: You should see a formatted Slack message with task details appearing within 10 seconds of the status change.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test webhook with both Ready for Review and Blocked status changes

Verify Slack messages include clickable task URLs

Configure error handling to log failed webhook attempts

Applies when: webhook

Set up monitoring alerts if webhook becomes inactive

Applies when: webhook

Document which ClickUp spaces have webhooks configured

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy n8n for this workflow

Use Power Automate for this if you're already in the Microsoft ecosystem and need tight integration with Teams alongside Slack. The webhook handling is solid and the condition logic works well for status filtering. Skip it if you need complex message formatting - Make handles rich Slack messages better.

Cost

This costs nothing at the free tier until you hit 750 runs per month. At 50 status changes daily, you'll use about 1,500 runs monthly = $15. Zapier would cost $20 for the same volume, while Make stays free up to 1,000 operations.

Tradeoffs

Zapier has better Slack formatting options with native support for blocks and attachments. Make offers more flexible webhook parsing and can handle multiple channel routing in one scenario. N8n gives you full JavaScript control over message templates. But Power Automate wins on enterprise security and compliance requirements that many IT departments demand.

You'll hit ClickUp's webhook reliability issues where endpoints go inactive without warning. Power Automate's condition logic gets clunky with complex status combinations - you'll end up with nested conditions that are hard to debug. The dynamic content picker sometimes loses webhook fields after editing, forcing you to regenerate the schema.

Ideas for what to build next

→
Add priority-based formatting — Use different Slack message colors or emoji based on ClickUp task priority levels.
→
Create digest notifications — Build a scheduled flow that sends daily summaries of all blocked tasks to management.
→
Expand to Teams integration — Add Microsoft Teams actions alongside Slack for organizations using both platforms.