How to Automatically Notify Slack When a ClickUp Task Changes Status Using Make.com

Introduction

If your team still depends on someone remembering to post project updates in Slack, you already know how messy it gets. Tasks move in ClickUp, somebody forgets to announce the change, and the next person in the chain keeps waiting because they never saw the update.

That usually turns into follow-up messages, status meetings, and “quick check-ins” that should not be necessary in the first place. A simple ClickUp to Slack automation fixes that by pushing the right update into the right channel the moment a task changes status.

By the end of this guide, you’ll know how to build a ClickUp to Slack status alert in Make.com, map the useful fields, and avoid the common setup mistakes.

What You’ll Need

• A ClickUp workspace with access to the Space, Folder, or List you want to monitor
• A Slack workspace with permission to post into the target channel
• A Make.com account
• A ClickUp API connection in Make.com
• A Slack connection in Make.com
• Ideally, a paid ClickUp or Make.com plan if you need higher automation volume or multiple scenario runs

How It Works

Here’s the logic in plain English: when a task in ClickUp changes status, Make.com watches for that event, pulls the task details, formats a message, and posts it into a Slack channel.

A good version of this automation does more than say “task updated.” It tells your team what changed, who owns it, what list it came from, and where to go next.

Step-by-Step Setup

1. Decide which ClickUp status changes should trigger the alert

Before you build anything, define the status changes you actually care about. For example:

• In Progress to Ready for Review
• Blocked to In Progress
• Waiting on Client to Ready to Send

If you alert on every single update, your Slack channel will turn into noise fast. Keep it focused on meaningful handoffs.

2. Create a new scenario in Make.com

In Make.com, create a new Scenario and add your first module.

Use the ClickUp module that watches for task changes in the list or folder you want to track. Depending on your ClickUp setup, this may be a watch or instant trigger module connected to task events.

If you are monitoring a single delivery team, start at the List level. If you need broader coverage, monitor the Folder or Space, but expect more filtering work later.

3. Filter the trigger so only status changes pass through

Add a filter immediately after the ClickUp trigger.

Set the condition to only continue when:

• the status field has changed, and
• the new status matches one of your target statuses

If your ClickUp trigger includes both old and new values, use those directly. If it only gives you the current task snapshot, you may need an extra ClickUp lookup step to compare the current status against the previous state.

This is the part most teams skip, then wonder why Slack gets flooded.

4. Pull the full task details

Add a ClickUp module to get the task details from the task ID provided by the trigger.

Map out the fields you want in Slack, usually:

• Task name
• Task URL
• Status
• Assignee
• Due date
• List name
• Priority, if your team uses it

This extra lookup is useful because trigger payloads often leave out the context your team actually needs.

5. Build the Slack message

Add the Slack module to post a message to a channel.

A clean message format looks like this:

Task: {{task name}}
Status: {{new status}}
Assignee: {{assignee name}}
Due date: {{due date}}
List: {{list name}}
Link: {{task URL}}

Keep the message scannable. Slack is not the place for a full project brief. The goal is to alert the right people and give them one click to open the task.

6. Choose the right Slack channel

Do not post everything into a general channel unless your team really works that way. Use a channel that matches the workflow, such as:

• #delivery-updates
• #client-x
• #ops-handoffs
• #review-needed

If you run client projects, channel-specific alerts are much cleaner than one giant project feed.

7. Test with a real task update

Run a test by changing the status of a task in ClickUp.

Check three things:

• The trigger fires only once
• The status filter catches the right transition
• The Slack message includes the fields your team needs

If the message looks messy, fix the formatting before turning the scenario on. A badly structured alert gets ignored quickly.

8. Turn the scenario on and monitor the first few runs

Once the test works, activate the scenario.

Watch the first few live updates closely. In Make.com, check execution logs for:

• Missing task IDs
• Empty assignee fields
• Tasks that skip the filter
• Slack permission issues

If your ClickUp tasks are heavily customised, pay attention to fields that may be optional or blank. That is usually where these setups break.

Real-World Business Scenario

A marketing agency using this setup can eliminate constant manual check-ins between account managers and designers. When a task moves to Ready for Review in ClickUp, the design channel in Slack gets the alert instantly, along with the task link and due date.

That means less hunting through boards, fewer “did you see this?” messages, and faster approvals. For a busy agency juggling multiple clients, that alone can save several hours a week in coordination time.

Common Variations

Notify only on high-priority tasks

Add a second filter so Slack alerts only fire when the task priority is set to urgent or high.

Mention the assignee automatically

If your team wants direct accountability, format the Slack message to include the assignee mention instead of just the name.

Send different messages for different statuses

Use a router in Make.com so Ready for Review, Blocked, and Done each post a slightly different message into Slack.

Conclusion + CTA

You now have a practical ClickUp to Slack automation that keeps status changes visible without extra manual updates. The workflow is simple, but it removes a real bottleneck: people only stay aligned when the update reaches them at the right moment.

If you want help building automations like this across ClickUp, Slack, Google Sheets, CRMs, or client delivery systems, Olmec Dynamics builds them for real businesses every week. You can see what we do at https://olmecdynamics.com.