

How to Send ClickUp Comment Notifications to Slack with Pipedream
Automatically post a Slack message to the project channel whenever someone adds a comment to 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
Development teams who live in Slack but track work in ClickUp and need instant comment visibility.
Not ideal for
Teams that prefer digest-style notifications or already get too many Slack messages.
Sync type
real-timeUse case type
notificationReal-World Example
A 12-person product team uses this to notify #project-alpha in Slack whenever someone comments on ClickUp tasks. Before automation, developers missed design feedback for hours because they rarely checked ClickUp directly. Now comments surface in Slack within 30 seconds.
What Will This Cost?
Drag the slider to your expected monthly volume.
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
Import this workflow directly into Pipedream
Copy the pre-built Pipedream blueprint and paste it straight into Pipedream. 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.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Task Name | ||
| Comment Text | ||
| Commenter Name | ||
| Task URL | ||
2 optional fieldsβΈ show
| Project/Space Name | |
| Comment Timestamp |
Step-by-Step Setup
Workflows > New
Create new Pipedream workflow
Go to pipedream.com and click Workflows in the left sidebar. Click the green New button in the top right. You'll see a blank workflow canvas with a trigger step waiting to be configured. This is where we'll connect ClickUp's webhook system.
- 1Click Workflows in the left navigation
- 2Click the green New button
- 3Click on the trigger step in the canvas
Trigger > Search Apps > ClickUp
Add ClickUp webhook trigger
In the trigger panel, search for ClickUp and select it. Choose New Task Comment from the event list. Pipedream will generate a unique webhook URL that ClickUp will send comment data to. Copy this URL - you'll need it for ClickUp configuration.
- 1Type 'ClickUp' in the app search box
- 2Select ClickUp from the results
- 3Choose 'New Task Comment' from the event dropdown
- 4Copy the webhook URL that appears
Trigger > Connect Account
Connect ClickUp account
Click Connect Account in the trigger step. A popup will ask for your ClickUp credentials. Sign in with the account that has admin access to the workspace where you want to monitor comments. Pipedream needs this to verify webhook authenticity.
- 1Click the Connect Account button
- 2Sign in with your ClickUp admin account
- 3Allow Pipedream access when prompted
- 4Wait for the green Connected status
ClickUp Settings > Integrations > Webhooks
Configure ClickUp webhook
Open ClickUp in a new tab and go to your workspace settings. Navigate to Integrations, then Webhooks. Click Add Webhook and paste the Pipedream URL you copied. Set the event to Task Comment Posted and choose which spaces to monitor. Most teams monitor all spaces to avoid missing comments.
- 1Go to ClickUp Settings (gear icon)
- 2Click Integrations in the left menu
- 3Select Webhooks tab
- 4Click Add Webhook
- 5Paste your Pipedream webhook URL
- 6Check 'Task Comment Posted' event
- 7Select spaces to monitor
Pipedream Workflow > Trigger Step
Test the ClickUp trigger
Add a test comment to any task in the monitored ClickUp spaces. Go back to Pipedream and click the trigger step - you should see the comment data appear in the test panel. This confirms ClickUp is successfully sending webhook data to Pipedream.
- 1Add a comment to any ClickUp task
- 2Return to your Pipedream workflow
- 3Click on the trigger step
- 4Wait 10-15 seconds for data to appear
Workflow > + > Slack
Add Slack action step
Click the + button below your trigger to add a new step. Search for Slack and select it. Choose Send Message to Channel from the actions list. This action will post the formatted comment notification to your chosen Slack channel.
- 1Click the + button below the trigger step
- 2Search for 'Slack' in the app list
- 3Select Slack from the results
- 4Choose 'Send Message to Channel'
Slack Step > Connect Account
Connect Slack account
Click Connect Account in the Slack step. Authorize Pipedream to access your Slack workspace. Make sure you're signed into the correct Slack workspace before authorizing. Pipedream needs permissions to post messages and read channel lists.
- 1Click Connect Account in the Slack step
- 2Choose your Slack workspace
- 3Click Allow on the permission screen
- 4Wait for connection confirmation
Slack Step > Channel
Configure Slack channel
Select the destination channel from the dropdown. Most teams create a dedicated channel like #clickup-comments or use existing project channels. The channel must be public or you need to invite the Pipedream bot first.
- 1Click the Channel dropdown
- 2Select your target channel
- 3If channel isn't listed, make it public or invite @pipedream
Slack Step > Message
Format the notification message
Click in the Message field and build your notification template. Use the trigger data to pull in comment text, task name, commenter name, and task URL. A good format: 'New comment on [task_name] by [user_name]: [comment_text] - [task_url]'. Reference the trigger step data using the $ syntax.
- 1Click in the Message text box
- 2Add static text like 'New comment on'
- 3Insert trigger data using the data selector
- 4Format with emojis or Slack markdown for readability
Workflow > Deploy
Test the complete workflow
Click Deploy in the top right to activate your workflow. Add another test comment to a ClickUp task and check your Slack channel. The notification should appear within 30 seconds with the comment details properly formatted.
- 1Click the Deploy button
- 2Wait for deployment confirmation
- 3Add a test comment in ClickUp
- 4Check your Slack channel for the notification
Add this Node.js code step between the ClickUp trigger and Slack action to filter out automated comments and format @mentions properly for Slack.
JavaScript β Code Stepexport default defineComponent({βΈ Show code
export default defineComponent({
async run({ steps, $ }) {
const comment = steps.trigger.event;... expand to see full code
export default defineComponent({
async run({ steps, $ }) {
const comment = steps.trigger.event;
// Skip automated comments from bots
if (comment.user.username.includes('bot') ||
comment.text.startsWith('Automated')) {
$.flow.exit('Skipping automated comment');
}
// Format ClickUp @mentions for Slack
let formattedText = comment.text;
const mentionRegex = /@\[(\w+\s\w+)\]/g;
formattedText = formattedText.replace(mentionRegex, '@$1');
// Truncate long comments
if (formattedText.length > 200) {
formattedText = formattedText.substring(0, 197) + '...';
}
// Build rich Slack message
const slackMessage = {
text: `π¬ New comment on *${comment.task.name}*`,
blocks: [{
type: 'section',
text: {
type: 'mrkdwn',
text: `π¬ *${comment.user.name}* commented on <${comment.task.url}|${comment.task.name}>:\n> ${formattedText}`
}
}]
};
return slackMessage;
}
});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
Use Pipedream for this if your team needs instant webhook processing and wants to customize the notification logic with code. The webhook response time averages 150ms, and you can filter comments, format @mentions, or route to different channels based on task properties. Skip Pipedream if you just want basic notifications without customization - Zapier's ClickUp integration handles simple cases faster.
At 500 comments per month, you'll use about 500 Pipedream credits (1 per comment). That's free on their starter plan. At 2000 comments monthly, you'll hit $19/month for the Developer plan. Zapier charges $20/month for the same volume, while Make stays free up to 1000 comments then jumps to $9/month.
Make has better built-in formatting tools for Slack messages without writing code. Zapier's ClickUp integration includes more filter options in the UI, so you don't need custom logic to skip automated comments. Power Automate integrates better if you're already using Microsoft Teams instead of Slack. But Pipedream wins on webhook reliability and lets you build complex comment routing logic that other platforms handle poorly.
You'll discover that ClickUp sends webhook data for comment edits and deletions too, not just new comments. The task URLs sometimes include query parameters that break in Slack, so strip everything after the task ID. Comment text arrives HTML-encoded, which looks ugly in Slack unless you decode entities like " and & in a preprocessing step.
Ideas for what to build next
- βAdd comment filtering β Insert a code step to skip notifications for internal comments, resolved threads, or comments from specific users like project managers.
- βCreate digest notifications β Build a scheduled workflow that sends a daily summary of all ClickUp comments instead of real-time notifications to reduce Slack noise.
- βEnable two-way sync β Add a second workflow that monitors Slack thread replies and posts them back as ClickUp comment responses to keep all discussion in one place.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup