Send a Teams alert when a ClickUp task is assigned using Make.com. Step-by-step trigger, payload, and field mapping for a production-ready ClickUp→Teams XPA.

Introduction

You want the assignee to see a short, actionable notification in Teams the moment a ClickUp task lands on their plate. Right now someone changes a task assignee in ClickUp and you rely on manual pings or noisy channel monitors. That costs time and creates missed handoffs.

This guide shows a minimal Make.com scenario that listens for ClickUp assignment changes and posts a concise message into a Teams channel or directly to a Teams user via an incoming webhook. By the end you will have a working ClickUp→Teams XPA that includes an Adaptive Card example and the exact field mappings to use.

First time you see XPA in this post, learn more about Cross-Platform Automation at our XPA overview: https://olmecdynamics.com/cross-platform-automation

What you will know by the end: which ClickUp webhook to use, what to check in the webhook payload, the Make.com modules to wire, and the Teams JSON body to send.

What You'll Need

ClickUp account with permissions to create Automations and webhooks in the Workspace you want to monitor
Microsoft Teams, permission to create an Incoming Webhook for the target channel, or a channel where the assigned user sees it
Make.com account, with HTTP module access (free plan works for light testing) and ClickUp connection if you prefer using built connectors for lookups
Basic knowledge of Adaptive Card JSON if you want richer formatting

Notes: ClickUp Automations that emit webhooks are available on standard plans. Teams incoming webhooks are enabled by creating a connector on the channel via the Teams app. If you need direct 1:1 messages to users use channel messages mentioning them or consider the Teams Bot route which is more complex.

How It Works (The Logic)

Trigger: ClickUp Automation webhook when a task is updated and the assignee changes. Make.com receives the webhook, parses the payload to find the task id, task name, new assignee and task URL. Then Make.com posts a JSON payload to the Teams Incoming Webhook URL, using either a simple text body or an Adaptive Card for actionable content.

In short: ClickUp webhook (assignee changed) → Make.com webhook receiver → format Teams message → HTTP POST to Teams webhook URL

Step-by-Step Setup

Create the ClickUp Automation webhook

In ClickUp, go to the Space or List where you want to watch assignment changes.
Create an Automation with trigger: Task Updated, add the condition: When Assignee changes, or when Assignee is set to any value.
Add action: Webhook, paste the Make.com custom webhook URL you will create in the next step. Configure the webhook to send full task payload including history items if available.

Common gotcha: if ClickUp’s automation editor offers a direct "When assignee changes" trigger use it. If it only offers Task Updated you must include a filter condition to limit runs to assignment changes.

Create a Make.com scenario and add a Custom Webhook trigger

In Make.com create a new Scenario.
Add the Webhooks module, choose Custom webhook and copy the URL.
Paste that URL into the ClickUp Automation webhook action.
Send a test assignment change in ClickUp so Make.com receives a sample payload.

What to inspect in the sample payload: event (usually "taskUpdated"), task.id, task.name, task.url, and history_items. history_items typically contains entries showing which field changed and the before and after values for the assignee.

Filter for assignee changes in Make.com

Immediately after the webhook trigger add a filter or conditional module that checks the payload. If ClickUp includes history_items, set the condition: any history_items contains field == "assignee". If history_items are not present, you can perform a lightweight ClickUp "Get Task" lookup and compare the current assignee against a stored value, but that is more complex.

Why this matters: without the filter you will post to Teams for every task update. Keep alerts limited to assignment events only.

Parse the new assignee details

From the webhook payload map the new assignee name and email if present. Often history_items will contain after with an array of assignee objects. Extract assignee.name and assignee.id.
Also map task.name and task.url for the message.

Gotcha: ClickUp payloads may list only user IDs. If you receive only an assignee id, add a ClickUp "Get User" or "Get Task" step to resolve the user name and email.

Build the Teams message body

Option A, minimal text message (works for most cases):

{ "text": "New task assigned to Jane Doe: Project kickoff — <https://app.clickup.com/t/123abc|Open task>" }

Option B, Adaptive Card for richer display (recommended for clearer context):

{ "type": "message", "attachments": [ { "contentType": "application/vnd.microsoft.card.adaptive", "content": { "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "type": "AdaptiveCard", "version": "1.2", "body": [ { "type": "TextBlock", "text": "New task assigned", "weight": "Bolder", "size": "Medium" }, { "type": "TextBlock", "text": "Task: {{task_name}}", "wrap": true }, { "type": "TextBlock", "text": "Assignee: {{assignee_name}}", "wrap": true }, { "type": "TextBlock", "text": "Due: {{due_date}}", "wrap": true } ], "actions": [ { "type": "Action.OpenUrl", "title": "Open task", "url": "{{task_url}}" } ] } } ] }

Replace the {{placeholders}} with Make.com data pills. The Adaptive Card gives a clear clickable button and structured fields in Teams.

Post to Teams using Make.com HTTP module

Add an HTTP module, method: POST.
In URL paste the Microsoft Teams incoming webhook URL you created on the channel.
Headers: Content-Type: application/json.
Body: put either the minimal text JSON or the Adaptive Card JSON. Use Make.com’s variable insertion to fill task_name, assignee_name, task_url and due_date.

Common gotcha: Teams incoming webhooks accept both simple text and Adaptive Card attachments. Keep the payload under the webhook size limit, roughly 28 KB.

Test with a real assignment change

In ClickUp change the assignee on a test task.
Confirm the Make.com scenario ran once, the filter identified an assignee change, and the Teams message appears formatted correctly.
Check the message for missing fields. If the assignee name is missing, add a ClickUp user lookup step before the HTTP module.

Turn the Scenario on and monitor

Enable the scenario and watch the first 24 runs. Look for false positives from other task updates and refine the filter if needed. Use Make.com run logs to debug payload mapping issues.

Real-World Business Scenario

A delivery team uses this XPA so product designers see a Teams card when an engineer assigns a QA task to them. The card includes task title, due date, and a single button to open the task. That replaced the manual Slack pings the team used and reduced missed handoffs during release weeks.

Because the message includes a link and the assignee name, the designer can open the task, read the brief, and respond without searching ClickUp.

Common Variations

Post to the assignee’s personal channel or chat: use a Teams Bot or Graph API to send direct messages. This requires Azure app registration and more permissions, so keep it for higher-value alerts only.
Add a small lookup to route messages to different Teams channels by project: store channel webhook URLs in a Google Sheet and select the right channel based on task.custom_field project tag.
Add a follow-up check: if the assignee does not comment within X hours, post a reminder into the team channel. This requires a scheduled scenario and a small state store.

Getting this live

You built a compact ClickUp→Teams XPA that fires only on assignee changes, resolves the necessary fields, and posts either a simple text message or an Adaptive Card into Teams via an incoming webhook. If you want this hardened for multi-team rollouts, user resolution across multiple ClickUp accounts, or direct Teams DM delivery using the Graph API, Olmec Dynamics builds these exact automations for businesses and can help deploy them across your workspace. See what we do at https://olmecdynamics.com

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