Intermediate~15 min setupProject Management & CommunicationVerified April 2026
ClickUp logo
Slack logo

How to Send ClickUp Comment Alerts to Slack with Power Automate

Automatically post to your Slack project channel whenever someone comments on a ClickUp task.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Best for

Teams that live in Slack but manage projects in ClickUp and need instant comment visibility

Not ideal for

Teams wanting comment digests or custom message formatting — Zapier handles those better

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 12-person marketing agency uses this to notify their #project-alpha channel whenever someone comments on ClickUp tasks. Before automation, team members checked ClickUp manually throughout the day and missed urgent feedback for hours. Now they respond to client comments within 15 minutes.

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

Skip the setup

Import this workflow directly into Power Automate

Copy the pre-built Power Automate blueprint and paste it straight into Power Automate. All modules, filters, and field mappings are already configured — you just need to connect your accounts.

Before You Start

Make sure you have everything ready.

ClickUp workspace admin access to create webhooks
Slack workspace member with ability to add apps
Power Automate license (included with most Microsoft 365 plans)

Optional

Target Slack channel already created

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Commenter Name
Task Name
Comment Text
3 optional fields▸ show
Task URL
Project Name
Comment Timestamp

Step-by-Step Setup

1

My flows > New flow > Automated cloud flow

Create a new automated flow

Go to make.powerautomate.com and click My flows in the left sidebar. Click New flow, then select Automated cloud flow. Name it 'ClickUp Comments to Slack' and leave the trigger selection for the next step.

  1. 1Click My flows in the left navigation
  2. 2Click the New flow button
  3. 3Select Automated cloud flow
  4. 4Type 'ClickUp Comments to Slack' as the flow name
  5. 5Click Skip on the trigger selection screen
What you should see: You should see the Power Automate designer with a blank automated flow ready for trigger configuration.
2

Flow designer > Choose your flow's trigger

Add the HTTP request trigger

Click the trigger box and search for 'HTTP'. Select 'When a HTTP request is received' from the results. This creates a webhook endpoint that ClickUp will call when comments are added.

  1. 1Click the trigger box labeled 'Choose your flow's trigger'
  2. 2Type 'HTTP' in the search bar
  3. 3Select 'When a HTTP request is received'
  4. 4Leave the JSON schema blank for now
What you should see: You'll see an HTTP trigger step with an empty Request Body JSON Schema field.
Common mistake — Don't add a JSON schema yet — you'll get the webhook URL first, then come back to configure the schema after testing.
Power Automate
+
click +
search apps
ClickUp
CL
ClickUp
Add the HTTP request trigger
ClickUp
CL
module added
3

Flow designer > Save

Save to generate webhook URL

Click Save in the top toolbar. Power Automate generates a unique webhook URL that appears in the HTTP trigger box. Copy this URL — you'll need it for ClickUp's webhook configuration.

  1. 1Click Save in the top toolbar
  2. 2Wait for the save confirmation
  3. 3Click into the HTTP trigger step
  4. 4Copy the HTTP POST URL that appears
What you should see: You should see a long webhook URL starting with https://prod-xx.eastus.logic.azure.com that you can copy.
Common mistake — Copy the webhook URL carefully — it expires if you regenerate it, and any scenarios using the old URL will silently stop working.
4

ClickUp Settings > Integrations > Webhooks

Configure ClickUp webhook

In ClickUp, go to your workspace settings and find Integrations. Click Webhooks, then Create Webhook. Set the endpoint to your Power Automate URL and select 'Task Comment Posted' as the event.

  1. 1Open ClickUp and click your workspace name in the top left
  2. 2Select Settings from the dropdown
  3. 3Click Integrations in the left sidebar
  4. 4Click the Webhooks tab
  5. 5Click Create Webhook
  6. 6Paste your Power Automate URL in the Endpoint field
  7. 7Check 'taskCommentPosted' in the Events list
  8. 8Click Create Webhook
What you should see: You should see your new webhook listed with a green Active status in ClickUp.
Common mistake — ClickUp webhook events use camelCase names — look for 'taskCommentPosted' not 'Task Comment Posted'.
5

ClickUp > Any Task > Comments

Test the webhook

Go to any ClickUp task and add a comment. This sends test data to your Power Automate flow. Check the flow's run history to see the incoming JSON structure from ClickUp.

  1. 1Open any ClickUp task in your workspace
  2. 2Scroll to the comments section
  3. 3Type a test comment like 'Testing webhook'
  4. 4Click Post Comment
  5. 5Return to Power Automate and refresh the page
What you should see: In Power Automate's run history, you should see a failed run with raw JSON data showing the comment details.
Common mistake — Copy the webhook URL carefully — it expires if you regenerate it, and any scenarios using the old URL will silently stop working.
Power Automate
▶ Test flow
executed
ClickUp
Slack
Slack
🔔 notification
received
6

Flow runs > Failed run > HTTP trigger

Add JSON schema

Click on the failed run in your flow history to see the JSON payload ClickUp sent. Copy this JSON, go back to your HTTP trigger, and click 'Use sample payload to generate schema'. Paste the JSON and click Done.

  1. 1Click on the most recent failed run
  2. 2Expand the HTTP trigger step
  3. 3Copy the entire JSON from the Body section
  4. 4Click Edit on your flow
  5. 5In the HTTP trigger, click 'Use sample payload to generate schema'
  6. 6Paste the JSON and click Done
What you should see: The HTTP trigger now shows a detailed JSON schema with fields like task_id, comment text, and user information.
Common mistake — Make sure to copy the complete JSON payload — missing fields will cause mapping issues later.
7

Flow designer > New step > Slack

Add Slack connection

Click New step below your trigger. Search for 'Slack' and select 'Post message' action. Power Automate prompts you to sign in to Slack and authorize the connection.

  1. 1Click New step below the HTTP trigger
  2. 2Type 'Slack' in the connector search
  3. 3Select the Slack connector
  4. 4Choose 'Post message' action
  5. 5Click Sign in when prompted
  6. 6Authorize Power Automate in Slack
What you should see: You should see the Slack Post message action with Channel and Message fields ready for configuration.
Common mistake — The Slack connector requires admin approval in some workspaces — check with your Slack admin if you get permission errors.
8

Slack action > Channel field

Configure channel selection

In the Channel field, click the dropdown to see your Slack channels. Select the project channel where you want comment notifications. If it doesn't appear, type the channel name manually with # prefix.

  1. 1Click the Channel dropdown in the Slack action
  2. 2Select your target channel from the list
  3. 3If not listed, type the channel name like '#project-alpha'
What you should see: The Channel field should show your selected channel name.
Common mistake — Map fields using the variable picker — don't type field names manually. Hand-typed variable names often have invisible spacing errors that produce blank output.
message template
🔔 New Record: {{name}} {{status}}
assignees[0].username: {{assignees[0].username}}
due_date: {{due_date}}
#sales
🔔 New Record: Jane Smith
Company: Acme Corp
9

Slack action > Message field > Dynamic content

Map comment data to message

Click in the Message field and build your notification using dynamic content. Add the commenter's name, task name, comment text, and task URL. Use the lightning bolt icon to insert fields from the ClickUp webhook data.

  1. 1Click in the Message field
  2. 2Type 'New comment by '
  3. 3Click the lightning bolt icon and select the commenter name field
  4. 4Add line breaks and type 'Task: '
  5. 5Insert the task name from dynamic content
  6. 6Add 'Comment: ' and insert the comment text
  7. 7Add the task URL for quick access
What you should see: Your message template should show a mix of plain text and blue dynamic content tags from ClickUp.
Common mistake — ClickUp's JSON uses nested objects — look for fields like history_items/0/comment/text_content rather than just 'comment'.
ClickUp fields
name
status
assignees[0].username
due_date
priority
available as variables:
1.props.name
1.props.status
1.props.assignees[0].username
1.props.due_date
1.props.priority
10

Flow designer > Save

Test the complete flow

Save your flow and add another comment to the same ClickUp task. The flow should run successfully and post a formatted message to your Slack channel within 30 seconds.

  1. 1Click Save in the top toolbar
  2. 2Go back to your ClickUp task
  3. 3Add another test comment
  4. 4Check your Slack channel for the notification
  5. 5Verify the message formatting looks correct
What you should see: Your Slack channel should receive a formatted message with the commenter name, task details, and comment text.

Add this expression in the Message field to format timestamps and handle missing task URLs gracefully. Paste it using the Expression tab in dynamic content.

JavaScript — Code Stepconcat(
▸ Show code
concat(
  'New comment by ', 
  body('Parse_JSON')?['history_items']?[0]?['user']?['username'],

... expand to see full code

concat(
  'New comment by ', 
  body('Parse_JSON')?['history_items']?[0]?['user']?['username'],
  '\n\nTask: ',
  body('Parse_JSON')?['task']?['name'],
  '\n\nComment: ',
  body('Parse_JSON')?['history_items']?[0]?['comment']?['text_content'],
  '\n\n',
  if(empty(body('Parse_JSON')?['task']?['url']), 'No task link available', body('Parse_JSON')?['task']?['url'])
)

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 n8n for this workflow

Use Power Automate for this if your team already lives in Microsoft 365 and you want native webhook handling without coding. The HTTP trigger processes ClickUp webhooks instantly and Slack posting happens within 15 seconds. Power Automate's expression builder handles JSON parsing better than Zapier's formatter. Skip this for complex message formatting — Zapier's Slack templates are more flexible.

Cost

Real math: Each comment costs 2 Power Automate actions (HTTP trigger + Slack post). At 200 comments/month that's 400 actions total. Most Microsoft 365 Business plans include 2,000 actions/month free, so you're covered. Zapier charges $20/month for the same volume on their Starter plan.

Tradeoffs

Zapier wins for message customization with built-in Slack formatting options and easier conditional logic. Make handles complex JSON parsing better with visual data mapping. n8n gives you unlimited runs if you self-host. But Power Automate's HTTP trigger is rock solid and the Slack connector rarely fails — I've seen 99.8% success rates on comment notifications.

You'll hit ClickUp's webhook payload inconsistencies first. Comment data nests differently for task comments versus subtask comments, breaking your JSON schema. The Slack connector sometimes drops markdown formatting from ClickUp comments. And Power Automate's expression editor makes debugging JSON paths painful compared to other platforms.

Ideas for what to build next

  • Add comment threadingModify the flow to post replies as Slack thread responses instead of separate messages for cleaner channels.
  • Filter by projectAdd conditions to only notify specific Slack channels based on which ClickUp list or folder the task belongs to.
  • Include task assigneesExtend the message format to mention Slack users when they're assigned to the commented task.

Related guides

Was this guide helpful?
ClickUp + Slack overviewPower Automate profile →