Why am I getting notifications for every task update, not just status changes?

ClickUp's Watch Task Updates trigger fires on any field change. Make sure your filter specifically checks the status field and only processes the exact status names you want to monitor.

Can I send different messages for Ready for Review vs Blocked status?

Yes, add a router module after your filter with separate paths for each status. Each path can have its own Slack message template and even target different channels.

How do I handle tasks that don't have assignees?

Use Make's if() function in your message template to show 'Unassigned' when the assignees field is empty. The code would be {{if(assignees.username; assignees.username; 'Unassigned')}}.

What happens if my Slack channel gets deleted or the bot gets removed?

Make will show error notifications and the scenario will stop processing. You'll need to update the channel selection or re-invite the Make bot to resume notifications.

Can I include custom field data from ClickUp in the notifications?

Yes, ClickUp's API includes custom fields in the task data. Map them in your Slack message using the custom field ID like {{custom_fields.field_id.value}}.

Beginner~12 min setupProject Management & CommunicationVerified April 2026

How to Send ClickUp Task Status Alerts to Slack with Make

Automatically notify your Slack channel whenever a ClickUp task moves 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.

Make

Also on:Zapier N8n Power-automate Pipedream

Best for

Teams that need filtered task status notifications and want visual control over the automation logic.

Not ideal for

Teams needing instant notifications or complex message formatting with rich media attachments.

Sync type

polling

Use case type

notification

Real-World Example

💡

A 12-person product team uses this to notify #dev-updates whenever ClickUp tasks move to Ready for Review or Blocked status. Before automation, developers checked ClickUp manually and often missed blocked tasks for hours. Now the team catches blockers within 15 minutes and reviews get picked up immediately by available team members.

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.

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 Make

Copy the pre-built Make blueprint and paste it straight into Make. 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 workspace admin access to generate API tokens

Slack workspace permission to install apps and create bots

Make account with available operations (free tier works for testing)

At least one ClickUp project with Ready for Review and Blocked statuses configured

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Task Name	`name`	The task title from ClickUp, used as the main identifier in Slack messages
Task Status	`status.status`	Current status name (Ready for Review, Blocked, etc.) - used for filtering and display
Task URL	`url`	Direct link to the ClickUp task for easy access from Slack

3 optional fields▸ show

Assignee Username	`assignees.username`	ClickUp username of task assignee - may be empty for unassigned tasks
Due Date	`due_date`	Task deadline timestamp - useful for urgent blocked task alerts
Priority	`priority.priority`	Task priority level (urgent, high, normal, low) for context in notifications

Step-by-Step Setup

Scenarios > Create new scenario > Add module

Create new scenario in Make

Set up your Make workspace and create a new scenario. This becomes your automation container where you'll add modules for ClickUp and Slack.

1Log into Make and click the blue 'Create a new scenario' button
2Click the large + icon in the center of the canvas
3Search for 'ClickUp' in the app search bar

✓ What you should see: You should see a list of ClickUp modules including triggers like 'Watch Task Updates' and 'Watch Tasks'.

ClickUp modules > Watch Task Updates

Add ClickUp Watch Task Updates trigger

Configure the trigger to monitor task status changes. This module polls ClickUp every few minutes for updated tasks in your workspace.

1Select 'Watch Task Updates' from the ClickUp module list
2Click 'Add' next to the Connection field to create a new ClickUp connection
3Enter your ClickUp API token and click 'Save'

✓ What you should see: The connection should show a green 'Verified' status and the module should be added to your canvas.

⚠

Common mistake — Don't use 'Watch Tasks' - that only fires for new tasks, not status changes on existing ones.

Make

click +

search apps

ClickUp

Add ClickUp Watch Task Updat…

ClickUp

module added

ClickUp module settings > Workspace > Space

Configure workspace and space selection

Tell ClickUp which workspace and spaces to monitor. You can watch all spaces or limit it to specific ones where status alerts matter.

1Select your workspace from the Workspace dropdown
2Choose 'All Spaces' or pick specific spaces you want to monitor
3Set the limit to 10 for testing (increase later for production)

✓ What you should see: The module should show your selected workspace name and either 'All Spaces' or your chosen space names.

⚠

Common mistake — Selecting too many high-activity spaces will burn through your operation limit quickly.

Module connection > Set up filter

Add status filter module

Create a filter to only process tasks that moved to Ready for Review or Blocked status. This prevents your Slack from getting flooded with every task change.

1Click the small wrench icon on the line between modules
2Select 'Set up a filter'
3Name the filter 'Status Filter' and set the condition

✓ What you should see: You should see a filter icon on the connection line between your modules.

⚠

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

trigger

filter

Status

matches criteria?

yes — passes through

no — skipped

Slack

notified

Filter settings > Conditions

Configure filter conditions

Set the exact status values to match. ClickUp passes status names as text strings, so the filter needs to catch both target statuses.

1Set Condition 1: status.status equals 'ready for review' (case insensitive)
2Click 'Add OR rule'
3Set Condition 2: status.status equals 'blocked' (case insensitive)

✓ What you should see: The filter should show two conditions connected with OR logic, checking for either status.

⚠

Common mistake — Status names must match exactly - check your ClickUp custom statuses for exact capitalization and spacing.

Add module > Slack > Create a Message

Add Slack Send Message module

Connect Slack to receive the notifications. This module posts messages to your chosen channel when the filter conditions are met.

1Click the + icon after your filter
2Search for 'Slack' and select it
3Choose 'Create a Message' from the Slack actions list

✓ What you should see: The Slack module should appear on your canvas after the filter.

⚠

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.

Message template

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

message template

🔔 New Record: {{name}} {{status}}
assignees[0].username: {{assignees[0].username}}
due_date: {{due_date}}

#sales

🔔 New Record: Jane Smith

Email: [email protected]

Company: Acme Corp

Slack module > Connection > Add new

Connect Slack workspace

Authenticate with your Slack workspace. Make needs permission to post messages to your channels on behalf of a bot user.

1Click 'Add' next to the Connection field
2Click 'Sign in with Slack' and authorize the Make app
3Verify the connection shows your correct workspace name

✓ What you should see: You should see a green connection status with your Slack workspace name displayed.

⚠

Common mistake — Make sure you're logged into the correct Slack workspace in your browser before authorizing.

Make settings

Connection

Choose a connection…Add

click Add

ClickUp

Authorize Make

popup window

✓

Connected

green checkmark

Slack module > Channel and Text settings

Configure channel and message content

Choose your target channel and build the notification message using ClickUp task data. The message should include task name, status, and assignee info.

1Select your target channel from the Channel dropdown
2In the Text field, click to add dynamic content from ClickUp
3Build message: '🔄 Task *{{name}}* moved to *{{status.status}}* - Assigned to {{assignees.username}}'

✓ What you should see: The message preview should show ClickUp field placeholders highlighted in blue.

⚠

Common mistake — Test with a channel you can easily monitor - don't use your main team channel until you verify it works.

Message template

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Slack module > Text field

Add task URL to message

Include a clickable link so team members can jump directly to the task. ClickUp provides a direct URL field in the webhook data.

1Add a new line in your message text
2Type '🔗 View task: ' followed by the ClickUp URL field
3The full message should include task name, status, assignee, and link

✓ What you should see: Your message template should show multiple ClickUp fields including the direct task URL.

⚠

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.

Message template

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Scenario controls > Run once

Test the scenario with sample data

Run a test to verify your modules connect properly and the filter works. Make will fetch recent ClickUp updates to test against.

1Click 'Run once' at the bottom of the scenario
2Wait for the ClickUp module to fetch recent task updates
3Check if any tasks match your status filter conditions

✓ What you should see: You should see execution results showing whether any tasks were processed or filtered out.

⚠

Common mistake — If no recent tasks match your status criteria, manually change a test task in ClickUp to Ready for Review first.

Make

▶ Run once

executed

✓

ClickUp

✓

Slack

🔔 notification

received

Slack channel > Make bot message

Verify Slack message format

Check that your test message appeared correctly in Slack with proper formatting and clickable links. The message should be clear and actionable.

1Go to your target Slack channel
2Look for the test message from Make bot
3Click the task URL to verify it opens the correct ClickUp task

✓ What you should see: You should see a formatted Slack message with task details and a working ClickUp link.

⚠

Common mistake — If the message looks broken, check that all ClickUp fields mapped correctly - missing assignees often cause formatting issues.

Message template

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Scenario settings > Toggle ON > Scheduling

Activate scenario for live monitoring

Turn on the scenario to start monitoring task status changes continuously. Set an appropriate polling interval based on how quickly you need notifications.

1Toggle the scenario to 'ON' in the bottom left
2Set the schedule to run every 15 minutes (or as needed)
3Save the scenario with a descriptive name like 'ClickUp Status Alerts'

✓ What you should see: The scenario should show 'ON' status and display your chosen schedule interval.

⚠

Common mistake — Don't set polling under 5 minutes unless you have high-volume plan - you'll hit operation limits fast.

Drop this into a Make custom function.

JavaScript — Custom Function{{if(assignees.username; "👤 " + assignees.username; "⚠️ Unassigned")}} | Priority: {{if(priority.priority; priority.priority; "None")}}

▸ Show code

{{if(assignees.username; "👤 " + assignees.username; "⚠️ Unassigned")}} | Priority: {{if(priority.priority; priority.priority; "None")}}

... expand to see full code

{{if(assignees.username; "👤 " + assignees.username; "⚠️ Unassigned")}} | Priority: {{if(priority.priority; priority.priority; "None")}}

Scaling Beyond 200+ task status changes per day+ Records

If your volume exceeds 200+ task status changes per day records, apply these adjustments.

Add deduplication storage

Use Make's data store to track processed task IDs and timestamps. This prevents duplicate notifications when tasks get multiple rapid updates within a few minutes.

Implement space-specific filtering

Instead of watching all spaces, create separate scenarios for different ClickUp spaces. This reduces processing load and allows team-specific Slack channels.

Batch processing for bulk updates

Add an iterator module after ClickUp to handle bulk status changes more efficiently. This is crucial when someone moves multiple tasks through workflow stages at once.

Going live

Production Checklist

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

Set error handling to 'Break' to catch API failures instead of silently skipping

Applies when: Always

Add rate limit handling for ClickUp API (100 requests/minute maximum)

Applies when: High volume

Test with actual task status changes, not just sample data from Make's test panel

Applies when: Always

Verify Slack bot permissions include channels where notifications will be sent

Applies when: Always

Set up data store deduplication if processing more than 50 task updates per day

Applies when: High volume

Configure scenario timeout to 40 seconds for workspaces with 1000+ tasks

Applies when: Enterprise

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Make for this workflow

Use Make for this if your team changes task statuses frequently and needs immediate Slack visibility. Make's ClickUp integration catches status changes within 5-15 minutes depending on your polling schedule, and the visual builder makes it easy to add filters for specific statuses. The webhook handling is more reliable than Zapier's ClickUp triggers. Skip Make if you need instant notifications - ClickUp's native Slack integration fires immediately but lacks the filtering control.

Cost

This workflow uses 2-3 operations per task status change: one to fetch the update, one for the filter check, and one to send the Slack message. At 100 status changes per month, that's 300 operations total. This fits comfortably in Make's free tier (1,000 operations/month). Zapier's free tier only gives you 100 tasks/month, so you'd need their $20 Starter plan. N8n self-hosted costs nothing but requires server maintenance.

Tradeoffs

Zapier's ClickUp integration includes more trigger options like 'Task Status Changed' instead of general updates, which reduces false positives. N8n offers better message templating with full HTML support for richer Slack formatting. But Make wins on the filtering capabilities - you can easily add complex conditions like team-specific notifications or priority-based routing without custom code. The visual flow makes it simple to modify logic later.

ClickUp's API sometimes delays status updates by 2-3 minutes, so don't expect instant notifications. The Watch Task Updates trigger pulls all field changes, not just status, so you'll process more data than needed - factor this into operation counts for high-activity workspaces. If team members change multiple fields quickly, you might get several notifications for the same task. Add a 5-minute deduplication filter using Make's data store if this becomes annoying.

Ideas for what to build next

→
Add priority-based routing — Create separate notification paths for high-priority blocked tasks that ping individual team members instead of just posting to the channel.
→
Build status change history log — Connect a Google Sheets module to track all status changes with timestamps for project reporting and team velocity analysis.
→
Set up auto-assignment alerts — Extend the workflow to notify specific team members when Ready for Review tasks match their expertise tags or project assignments.