

How to Send ClickUp Task Status Changes to Slack with Zapier
Auto-notify Slack channels when ClickUp tasks move 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.
Best for
Teams using ClickUp and Slack who need instant notifications when tasks hit review or blocker states.
Not ideal for
Teams needing complex approval workflows or wanting to store notification history in databases.
Sync type
real-timeUse case type
notificationReal-World Example
A 12-person product team uses this to notify #dev-review when tasks move to Ready for Review and #urgent when tasks hit Blocked status. Before automation, developers checked ClickUp manually throughout the day and blocked tasks sat unnoticed for hours. Now review requests get immediate attention and blockers surface instantly to the team lead.
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
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Task Name | name | |
| Status | status.status | |
| Task URL | url | |
4 optional fieldsβΈ show
| Assignee Name | assignees[0].username |
| Due Date | due_date |
| Priority | priority.priority |
| Project Name | list.name |
Step-by-Step Setup
Dashboard > Create Zap > Trigger
Create new Zap and connect ClickUp
Start a new Zap in Zapier and select ClickUp as your trigger app. You'll authenticate your ClickUp account to allow Zapier to monitor task changes.
- 1Click 'Create Zap' from your Zapier dashboard
- 2Search for 'ClickUp' in the trigger app dropdown
- 3Select 'Task Updated' as your trigger event
- 4Click 'Continue' to proceed to account connection
Trigger > Account Connection
Authenticate ClickUp account
Connect your ClickUp workspace to Zapier using your account credentials. This gives Zapier read access to monitor task status changes across your workspace.
- 1Click 'Sign in to ClickUp' button
- 2Enter your ClickUp email and password
- 3Click 'Authorize' to grant Zapier access
- 4Select your workspace from the dropdown if you have multiple
Trigger > Set up trigger
Configure trigger filters
Set up the trigger to only fire for specific status changes. You'll filter for tasks moving to 'Ready for Review' or 'Blocked' status to avoid noise from other updates.
- 1Select your Space from the dropdown menu
- 2Choose your specific List or leave as 'Any List'
- 3In the 'Status' field, select 'Ready for Review'
- 4Click 'Add OR condition' and select 'Blocked' as second status
Trigger > Test
Test ClickUp trigger
Zapier will pull in a recent task update to use as sample data. If no recent updates exist, you'll need to manually change a task status to generate test data.
- 1Click 'Test trigger' button
- 2Wait for Zapier to fetch recent task updates
- 3Review the sample data that appears
- 4Click 'Continue with selected record' if data looks correct
Action > Choose App & Event
Add Slack as action app
Now you'll set up Slack to receive the notifications. Choose the 'Send Channel Message' action to post updates to your team channels.
- 1Click the + button to add an action step
- 2Search for and select 'Slack' from the app list
- 3Choose 'Send Channel Message' as the action event
- 4Click 'Continue' to proceed to account setup
Action > Account Connection
Connect Slack workspace
Authenticate your Slack workspace so Zapier can post messages. You'll need admin permissions or the ability to install apps in your workspace.
- 1Click 'Sign in to Slack' button
- 2Select your Slack workspace from the list
- 3Click 'Allow' to grant Zapier posting permissions
- 4Verify your workspace name appears in Zapier
Action > Set up action
Configure Slack message details
Set up which channel receives notifications and customize the message format. You'll map ClickUp task data into a readable Slack message format.
- 1Select the destination channel from the dropdown
- 2In 'Message Text', click the + icon to add ClickUp fields
- 3Insert 'Task Name' and 'Status' from the ClickUp data
- 4Add 'Task URL' so team members can click through to the task
π¬ New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Action > Message Configuration
Customize message format
Create a message template that includes task details and context. Good formatting helps your team quickly understand what needs attention without clicking through.
- 1Format your message like: 'Task [Task Name] is now [Status]'
- 2Add assignee info using the 'Assignee Name' field
- 3Include the clickable task URL at the end
- 4Set Bot Name to 'ClickUp Updates' for clarity
π¬ New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Action > Test
Test Slack action
Send a test message to your Slack channel using the sample ClickUp data. This verifies your formatting and permissions work correctly.
- 1Click 'Test action' button
- 2Wait for the test message to send
- 3Check your Slack channel for the test notification
- 4Verify the message format and data look correct
Steps > Add Paths
Add status filtering logic
Create conditional logic to send different messages or route to different channels based on status type. Ready for Review vs Blocked statuses often need different team attention.
- 1Click + to add a Paths step after ClickUp trigger
- 2Create Path A with condition 'Status equals Ready for Review'
- 3Create Path B with condition 'Status equals Blocked'
- 4Move your Slack action under the appropriate path
Paths > Individual Path Configuration
Configure different channels per status
Route Ready for Review tasks to your review team channel and Blocked tasks to a priority channel. This ensures the right people see urgent vs routine notifications.
- 1In Path A, set Slack channel to #reviews or similar
- 2In Path B, set Slack channel to #urgent or #blocked-tasks
- 3Customize message text for each path appropriately
- 4Test both paths with different status scenarios
Zap Settings > Publish
Turn on Zap and monitor
Activate your Zap and watch the task history to ensure notifications fire correctly. Monitor for the first few status changes to catch any issues early.
- 1Click 'Publish' to activate your Zap
- 2Change a test task to 'Ready for Review' in ClickUp
- 3Verify the Slack notification appears within 2-3 minutes
- 4Check the Zap history for any errors or skipped runs
Drop this into a Zapier Code step.
JavaScript β Code Step{{status__status}} != {{status__previous_status}} AND ({{status__status}} = "ready for review" OR {{status__status}} = "blocked")βΈ Show code
{{status__status}} != {{status__previous_status}} AND ({{status__status}} = "ready for review" OR {{status__status}} = "blocked")... expand to see full code
{{status__status}} != {{status__previous_status}} AND ({{status__status}} = "ready for review" OR {{status__status}} = "blocked")Scaling Beyond 300+ status changes/day+ Records
If your volume exceeds 300+ status changes/day records, apply these adjustments.
Add deduplication filtering
ClickUp sends duplicate webhooks during bulk operations. Add a Storage step to track recent task IDs and skip duplicates within 60 seconds. This prevents notification spam during mass status updates.
Implement webhook retry logic
High volume can overwhelm ClickUp's webhook delivery. Add a Delay step after the trigger and enable automatic retries in Zap settings. This handles temporary delivery failures without losing notifications.
Split by workspace sections
Create separate Zaps for different ClickUp teams or folders instead of one master Zap. This distributes webhook load and makes troubleshooting easier when specific teams have issues.
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 Zapier for this if your team lives in Slack and needs instant visibility on task blockers. Setup takes under 20 minutes and the webhook-based trigger fires within 2 minutes of status changes. The guided interface makes it simple to route different statuses to different channels without code. Skip Zapier if you need complex conditional logic or want to store notification history β Make handles multi-step decision trees better.
This workflow burns 1 task per status change. At 200 status changes per month, that's 200 tasks total. The Starter plan at $20/month includes 750 tasks, so you're covered with room to grow. Make would cost $9/month for the same volume but requires more technical setup. N8n is free for this volume but you'll spend 3x longer configuring the ClickUp webhooks manually.
Make beats Zapier on conditional routing β its visual branches handle complex status workflows better than Zapier's Paths feature. N8n wins on customization since you can write JavaScript to format messages exactly how you want them. But Zapier's ClickUp integration gets webhook updates faster and more reliably. The pre-built Slack formatter also handles @ mentions and channel routing without custom code.
You'll hit ClickUp's webhook quirks after going live. The API sometimes sends duplicate status change events within seconds β add a 30-second delay filter to dedupe them. Task updates in bulk (like mass status changes) can overwhelm Zapier's webhook endpoint and cause some to fail silently. ClickUp also doesn't send webhooks for status changes made via their mobile app consistently, so some updates get missed entirely.
Ideas for what to build next
- βAdd task completion notifications β Create a second Zap that notifies when Ready for Review tasks move to Done status. This closes the feedback loop for reviewers.
- βCreate blocked task escalation β Build a delayed follow-up that tags managers if tasks stay Blocked for more than 24 hours. Use Zapier's Delay and Paths features.
- βTrack notification metrics in Sheets β Log all status change notifications to Google Sheets for reporting on team review times and common blockers. Helps identify workflow bottlenecks.
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