Beginner~8 min setupProject Management & CommunicationVerified April 2026
ClickUp logo
Slack logo

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

Use case type

notification

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

/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

Before You Start

Make sure you have everything ready.

ClickUp workspace with admin or member access (not guest)
Slack workspace where you can install apps or have Zapier pre-approved
Target Slack channels already created (#reviews, #blocked-tasks, etc.)
Active Zapier account with available task quota
At least one ClickUp task with custom statuses including Ready for Review and Blocked

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Task Namename
Statusstatus.status
Task URLurl
4 optional fieldsβ–Έ show
Assignee Nameassignees[0].username
Due Datedue_date
Prioritypriority.priority
Project Namelist.name

Step-by-Step Setup

1

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.

  1. 1Click 'Create Zap' from your Zapier dashboard
  2. 2Search for 'ClickUp' in the trigger app dropdown
  3. 3Select 'Task Updated' as your trigger event
  4. 4Click 'Continue' to proceed to account connection
βœ“ What you should see: You should see ClickUp selected as your trigger with 'Task Updated' event chosen.
2

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.

  1. 1Click 'Sign in to ClickUp' button
  2. 2Enter your ClickUp email and password
  3. 3Click 'Authorize' to grant Zapier access
  4. 4Select your workspace from the dropdown if you have multiple
βœ“ What you should see: Green checkmark appears next to ClickUp with your workspace name displayed.
⚠
Common mistake β€” Don't use a guest account β€” you need workspace admin or member access to receive task webhooks.
3

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.

  1. 1Select your Space from the dropdown menu
  2. 2Choose your specific List or leave as 'Any List'
  3. 3In the 'Status' field, select 'Ready for Review'
  4. 4Click 'Add OR condition' and select 'Blocked' as second status
βœ“ What you should see: Trigger configuration shows two status conditions with OR logic between them.
⚠
Common mistake β€” ClickUp sends webhooks for ALL task updates β€” filtering here prevents your Zap from running on irrelevant changes like assignee or due date edits.
ClickUp
CL
trigger
filter
Condition
matches criteria?
yes β€” passes through
no β€” skipped
Slack
SL
notified
4

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.

  1. 1Click 'Test trigger' button
  2. 2Wait for Zapier to fetch recent task updates
  3. 3Review the sample data that appears
  4. 4Click 'Continue with selected record' if data looks correct
βœ“ What you should see: Sample task data appears showing task name, status, assignee, and other ClickUp fields.
⚠
Common mistake β€” If no data appears, go change a task to 'Ready for Review' in ClickUp, then click 'Test trigger' again.
Zapier
β–Ά Turn on & test
executed
βœ“
ClickUp
βœ“
Slack
Slack
πŸ”” notification
received
5

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.

  1. 1Click the + button to add an action step
  2. 2Search for and select 'Slack' from the app list
  3. 3Choose 'Send Channel Message' as the action event
  4. 4Click 'Continue' to proceed to account setup
βœ“ What you should see: Slack appears as your action app with 'Send Channel Message' selected.
6

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.

  1. 1Click 'Sign in to Slack' button
  2. 2Select your Slack workspace from the list
  3. 3Click 'Allow' to grant Zapier posting permissions
  4. 4Verify your workspace name appears in Zapier
βœ“ What you should see: Slack connection shows green checkmark with your workspace name displayed.
⚠
Common mistake β€” If you can't install the Zapier app, ask a Slack admin to pre-approve it in your workspace settings.
Zapier settings
Connection
Choose a connection…Add
click Add
ClickUp
Log in to authorize
Authorize Zapier
popup window
βœ“
Connected
green checkmark
7

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.

  1. 1Select the destination channel from the dropdown
  2. 2In 'Message Text', click the + icon to add ClickUp fields
  3. 3Insert 'Task Name' and 'Status' from the ClickUp data
  4. 4Add 'Task URL' so team members can click through to the task
βœ“ What you should see: Message preview shows ClickUp task data formatted as a Slack message.
⚠
Common mistake β€” Private channels won't appear in the dropdown unless you manually invite the Zapier bot to them first.
Message template
πŸ“¬ New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}
8

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.

  1. 1Format your message like: 'Task [Task Name] is now [Status]'
  2. 2Add assignee info using the 'Assignee Name' field
  3. 3Include the clickable task URL at the end
  4. 4Set Bot Name to 'ClickUp Updates' for clarity
βœ“ What you should see: Message template shows dynamic fields that will populate with actual task data.
⚠
Common mistake β€” Don't use @channel or @here mentions β€” status changes happen frequently and will create notification fatigue.
Message template
πŸ“¬ New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}
9

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.

  1. 1Click 'Test action' button
  2. 2Wait for the test message to send
  3. 3Check your Slack channel for the test notification
  4. 4Verify the message format and data look correct
βœ“ What you should see: Test message appears in your Slack channel with properly formatted task information.
⚠
Common mistake β€” Test messages are real posts β€” use a test channel first, then change to your production channel later.
10

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.

  1. 1Click + to add a Paths step after ClickUp trigger
  2. 2Create Path A with condition 'Status equals Ready for Review'
  3. 3Create Path B with condition 'Status equals Blocked'
  4. 4Move your Slack action under the appropriate path
βœ“ What you should see: Zap shows branching paths with different conditions for each status type.
⚠
Common mistake β€” Without paths, both status types go to the same channel with identical messages β€” this creates confusion about urgency levels.
11

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.

  1. 1In Path A, set Slack channel to #reviews or similar
  2. 2In Path B, set Slack channel to #urgent or #blocked-tasks
  3. 3Customize message text for each path appropriately
  4. 4Test both paths with different status scenarios
βœ“ What you should see: Each path shows different target channels and customized message formats.
⚠
Common mistake β€” Create the target Slack channels first β€” Zapier can't auto-create channels and will fail if they don't exist.
12

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.

  1. 1Click 'Publish' to activate your Zap
  2. 2Change a test task to 'Ready for Review' in ClickUp
  3. 3Verify the Slack notification appears within 2-3 minutes
  4. 4Check the Zap history for any errors or skipped runs
βœ“ What you should see: Zap shows 'On' status and task history shows successful runs when status changes occur.

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.

1

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.

2

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.

3

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

VerdictWhy Zapier for this workflow

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.

Cost

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.

Tradeoffs

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

Was this guide helpful?
← ClickUp + Slack overviewZapier profile β†’