How to Notify Slack When a ClickUp Task Is Assigned Using Make.com

Introduction

If ClickUp tasks are getting assigned but your Slack channel stays quiet, you get a predictable chain reaction. People miss work, handoffs stall, and someone ends up posting “who owns this?” in the wrong place.

A Cross-Platform Automation (XPA) solves it by turning the assignment event into a Slack alert the moment the task is assigned. In this guide, you will learn how to build a Make.com workflow that detects assignments in ClickUp, filters to the cases you care about, and posts a clean Slack message with a working task link.

What You'll Need

• ClickUp access to the Workspace/Space/Folder or List you want to watch
• Slack access to the channel where you want alerts posted
• A Make.com account
• Make.com connections for ClickUp and Slack
• ClickUp permissions so Make.com can read task fields and capture assignment details

How It Works (The Logic)

When ClickUp emits an event for a task update, Make.com evaluates the payload to see whether the task is now assigned (or the assignee changed). If the assignee matches your rules, Make.com posts a Slack message to your selected channel.

Trigger → filter (assignee rules) → (optional) fetch full task details → Slack post.

Step-by-Step Setup

1. Define the assignment rule you want to automate

Don’t start with “every update.” Start with a rule like:

• Alert when the assignee is set (non-empty)
• Alert when the assignee changes to a specific user or a specific team of users
• Alert when a task enters a specific List and gets assigned there

A simple version that works for most teams: notify when an assignee value is present, then later you tighten it.

2. Create a new scenario in Make.com

In Make.com:

1. Create a new scenario
2. Add the ClickUp watch/trigger module for task updates or task changes
3. Point it at the correct scope (Space/Folder/List)

Tip: keep the scope narrow at first. If you watch the entire Space, your filter will have to work harder.

3. Add a filter to reduce Slack noise

Immediately after the ClickUp trigger, add a Make.com Filter module.

Use a condition like:

• Continue only if assignee is not empty

If you want targeted routing, add conditions such as:

• Continue only if assignee equals TARGET_ASSIGNEE_ID (or the matching user identifier your trigger exposes)

Common gotcha: Make.com may expose the assignee field under a nested path (for example something like assignee.user.name or assignee.id). If your filter never passes, inspect one real execution payload and adjust the field path.

4. (Optional) Fetch full task details for a better Slack message

Many “watch” triggers return partial data. If your Slack message needs fields that are missing, add a second ClickUp module to get the task by ID.

Fetch:

• Task name
• Task URL or a reliable task permalink
• Due date (if your workflow uses it)
• Priority (if your workflow uses it)
• Assignee display name

This makes the Slack alert consistent even when the trigger payload is minimal.

5. Configure the Slack “post message” action

Add a Slack module to post a message.

Message template (keep it scannable):

• Task: {{task name}}
• Assigned to: {{assignee name}}
• Due: {{due date}}
• Priority: {{priority}}
• Link: {{task url}}

Avoid multi-paragraph messages. People read Slack on phones, so keep it one tight block.

6. Choose the right channel

Pick a channel that matches how your team works.

Good examples:

• #delivery-ops for ops handoffs
• #content-delivery for content owners
• #engineering-work for engineering execution

If you want a single channel, keep the alert highly filtered. Otherwise you recreate the same noise problem you started with.

7. Test with two real assignment changes

Run tests with:

• A task that gets assigned to someone who should trigger the alert
• A task update that does not re-assign (for example comment-only), and confirm it does not post

This validates your filter logic and prevents duplicate or unwanted notifications.

8. Turn it on and review the first few logs

After activation:

• Check Make.com execution logs for filter misses
• Confirm that task url is populated (linking failures make the automation feel broken)
• Watch for blank due dates or missing priority and adjust the task fetch mapping if needed

Real-World Business Scenario

A small product marketing team runs ClickUp with an “Intake” List and a “Delivery” List. When a task moves into Delivery and becomes assigned to the copywriter, the team posts an alert into #content-delivery.

Outcome: the writer stops waiting for updates, managers stop repeating status in Slack, and the due date is visible in the first message. That reduces “where are we with this?” pings, which is usually where coordination time quietly disappears.

If your workflow also needs status change alerts, you can combine assignment alerts with status-based notifications. For a related pattern, see how we built Slack alerts for ClickUp status changes.

Common Variations

1) Route different assignees to different channels

Add a router after the filter.

• If assignee belongs to Team A, post into #team-a
• If assignee belongs to Team B, post into #team-b

2) Only notify when priority is High or Urgent

Add an extra filter condition on priority.

This keeps your channel useful when assignments happen frequently.

3) Add a follow-up message when due date is set

If due dates are added after assignment, create a second scenario triggered by due date being populated, then post a reminder.

The working automation you built

You now have a Make.com scenario that detects when a ClickUp task is assigned, filters to the assignment events you care about, and posts a targeted Slack alert with the task link and key fields.

That is Cross-Platform Automation (XPA) in practice: fewer manual updates, faster handoffs, and a message your team can act on immediately. Olmec Dynamics builds these systems across ClickUp, Slack, Google Sheets, CRMs, and document workflows. Start with the overview of Cross-Platform Automation (XPA), and then see what we do here.