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

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-time

Use case type

notification

Real-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.

/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 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.

Admin access to the ClickUp workspace where you want to monitor comments
Permission to add integrations and webhooks in ClickUp workspace settings
Access to post messages in the target Slack channel or ability to make it public
Slack workspace admin rights or pre-approval for adding the Pipedream app

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Task Name
Comment Text
Commenter Name
Task URL
2 optional fieldsβ–Έ show
Project/Space Name
Comment Timestamp

Step-by-Step Setup

1

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.

  1. 1Click Workflows in the left navigation
  2. 2Click the green New button
  3. 3Click on the trigger step in the canvas
βœ“ What you should see: You should see a trigger configuration panel open on the right side.
2

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.

  1. 1Type 'ClickUp' in the app search box
  2. 2Select ClickUp from the results
  3. 3Choose 'New Task Comment' from the event dropdown
  4. 4Copy the webhook URL that appears
βœ“ What you should see: You should see a webhook URL like https://xxx.m.pipedream.net displayed in the trigger configuration.
⚠
Common mistake β€” Don't test the trigger yet - ClickUp needs to be configured first or you'll get timeout errors.
Pipedream
+
click +
search apps
ClickUp
CL
ClickUp
Add ClickUp webhook trigger
ClickUp
CL
module added
3

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.

  1. 1Click the Connect Account button
  2. 2Sign in with your ClickUp admin account
  3. 3Allow Pipedream access when prompted
  4. 4Wait for the green Connected status
βœ“ What you should see: You should see 'Connected' with a green checkmark next to your ClickUp account name.
⚠
Common mistake β€” Use an admin account, not a guest user - webhooks require workspace admin permissions.
Pipedream settings
Connection
Choose a connection…Add
click Add
ClickUp
Log in to authorize
Authorize Pipedream
popup window
βœ“
Connected
green checkmark
4

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.

  1. 1Go to ClickUp Settings (gear icon)
  2. 2Click Integrations in the left menu
  3. 3Select Webhooks tab
  4. 4Click Add Webhook
  5. 5Paste your Pipedream webhook URL
  6. 6Check 'Task Comment Posted' event
  7. 7Select spaces to monitor
βœ“ What you should see: You should see the webhook listed as Active with a green status indicator.
⚠
Common mistake β€” If you select too many spaces, you'll get notifications for internal comments that don't need Slack alerts.
5

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.

  1. 1Add a comment to any ClickUp task
  2. 2Return to your Pipedream workflow
  3. 3Click on the trigger step
  4. 4Wait 10-15 seconds for data to appear
βœ“ What you should see: You should see JSON data containing the comment text, task name, user info, and task URL.
Pipedream
β–Ά Deploy & test
executed
βœ“
ClickUp
βœ“
Slack
Slack
πŸ”” notification
received
6

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.

  1. 1Click the + button below the trigger step
  2. 2Search for 'Slack' in the app list
  3. 3Select Slack from the results
  4. 4Choose 'Send Message to Channel'
βœ“ What you should see: You should see a new Slack step added to your workflow canvas.
⚠
Common mistake β€” Don't choose 'Send Direct Message' unless you want to spam individual users with every comment.
7

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.

  1. 1Click Connect Account in the Slack step
  2. 2Choose your Slack workspace
  3. 3Click Allow on the permission screen
  4. 4Wait for connection confirmation
βœ“ What you should see: You should see your Slack workspace name with a Connected status.
⚠
Common mistake β€” If you're in multiple Slack workspaces, double-check you're connecting the right one.
8

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.

  1. 1Click the Channel dropdown
  2. 2Select your target channel
  3. 3If channel isn't listed, make it public or invite @pipedream
βœ“ What you should see: You should see your chosen channel selected in the dropdown.
⚠
Common mistake β€” Private channels won't appear unless you invite the Pipedream app to them first.
9

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.

  1. 1Click in the Message text box
  2. 2Add static text like 'New comment on'
  3. 3Insert trigger data using the data selector
  4. 4Format with emojis or Slack markdown for readability
βœ“ What you should see: You should see a message template with both static text and dynamic trigger data fields.
⚠
Common mistake β€” Don't include sensitive task details if the Slack channel has external guests.
10

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.

  1. 1Click the Deploy button
  2. 2Wait for deployment confirmation
  3. 3Add a test comment in ClickUp
  4. 4Check your Slack channel for the notification
βœ“ What you should see: You should see a properly formatted notification appear in your Slack channel.

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

VerdictWhy n8n for this workflow

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.

Cost

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.

Tradeoffs

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 &quot; and &amp; 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

Was this guide helpful?
← ClickUp + Slack overviewPipedream profile β†’