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

How to Create ClickUp Tasks from Slack with Power Automate

React to a Slack message with an emoji to automatically create a ClickUp task with the message content as the description.

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

Best for

Teams that triage requests in Slack channels and want tasks created without switching apps

Not ideal for

Teams needing complex task hierarchies or custom field population from message parsing

Sync type

real-time

Use case type

routing

Real-World Example

💡

A 12-person product team uses this to convert feature requests from their #feedback channel into ClickUp tasks. When someone reacts with 📝 emoji to a customer message, it creates a task in their Feature Requests list with the original message as description. Before automation, PMs copied messages manually twice per day and lost track of requests during busy periods.

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.

Slack workspace admin access or permission to install apps
ClickUp workspace with create task permissions in target lists
Microsoft Power Automate account (works with free tier)
Access to ClickUp Team ID and List ID values from target workspace

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Task Name
List ID
Team ID
4 optional fields▸ show
Description
Priority
Tags
Due Date

Step-by-Step Setup

1

Home > Create > Automated cloud flow

Create new automated cloud flow

Log into make.powerautomate.com and click Create in the left sidebar. Choose Automated cloud flow from the options. Name your flow something like 'Slack to ClickUp Task Creation'. You'll see the flow designer with a trigger placeholder waiting for configuration.

  1. 1Click Create in the left sidebar
  2. 2Select 'Automated cloud flow'
  3. 3Name it 'Slack to ClickUp Task Creation'
  4. 4Click Create without selecting a trigger yet
What you should see: You should see a blank flow canvas with 'Choose your flow's trigger' at the top.
2

Flow designer > Choose trigger > Slack

Add Slack reaction trigger

Click the trigger box and search for 'Slack' in the connector list. Select the 'When a reaction is added (V2)' trigger. This trigger fires instantly when someone adds any emoji reaction to a message. You'll need to sign in to your Slack workspace if you haven't connected before.

  1. 1Click 'Choose your flow's trigger'
  2. 2Search for 'Slack' and select it
  3. 3Choose 'When a reaction is added (V2)' trigger
  4. 4Sign in to your Slack workspace when prompted
What you should see: The trigger shows 'When a reaction is added (V2)' with Slack connection established.
Common mistake — The V1 trigger is deprecated and missing key fields like message text. Always use V2.
Power Automate
+
click +
search apps
ClickUp
CL
ClickUp
Add Slack reaction trigger
ClickUp
CL
module added
3

Trigger configuration

Configure Slack trigger settings

Select the Slack team from the dropdown that appears after authentication. Leave the Channel field blank to monitor all channels, or pick a specific channel if you only want reactions from one place. The Item field should stay as 'message' since we're watching for reactions on messages, not files or other items.

  1. 1Select your Slack workspace from the Team dropdown
  2. 2Leave Channel blank for all channels or select specific channel
  3. 3Keep Item as 'message'
  4. 4Click Save
What you should see: The trigger shows your selected team and channel configuration with a green checkmark.
4

Flow designer > New step > Control

Add condition to filter specific emoji

Click New step below the trigger and search for 'Condition' in the control actions. We need to filter for only the emoji you want to trigger task creation. In the condition box, select 'Reaction' from dynamic content (it comes from the Slack trigger). Set it equal to the emoji name like 'memo' for 📝 or 'white_check_mark' for ✅.

  1. 1Click '+ New step' below the trigger
  2. 2Search for 'Condition' and select it
  3. 3Click the left condition box and select 'Reaction' from dynamic content
  4. 4Set operator to 'is equal to'
  5. 5Type the emoji name like 'memo' in the right box
What you should see: Condition shows 'If reaction is equal to memo' with Yes/No branches.
Common mistake — Use emoji names like 'memo', not the actual emoji symbols. Check Slack's emoji picker for exact names.
ClickUp
CL
trigger
filter
Condition
matches criteria?
yes — passes through
no — skipped
Slack
SL
notified
5

Condition > Yes > Add an action

Connect to ClickUp in Yes branch

Click Add an action inside the Yes branch of the condition. Search for ClickUp in the connectors list and select it. You'll see several ClickUp actions available. Choose 'Create Task' as this matches our goal. Sign in to your ClickUp account when the authentication dialog appears.

  1. 1Click 'Add an action' in the Yes branch
  2. 2Search for 'ClickUp' and select the connector
  3. 3Choose 'Create Task' action
  4. 4Sign in to ClickUp when prompted
What you should see: ClickUp Create Task action appears with authentication completed and field inputs visible.
6

Create Task action configuration

Configure ClickUp task creation

Fill in the required ClickUp fields. Team ID and List ID are required - you can find these in ClickUp by going to your list settings and copying the ID from the URL. For Task Name, use a combination of static text like 'Slack Request: ' plus the dynamic 'User' field from Slack trigger. This creates descriptive task titles.

  1. 1Enter your ClickUp Team ID (find in list URL)
  2. 2Enter your target List ID
  3. 3Set Task Name to 'Slack Request: ' + User (dynamic content)
  4. 4Leave Priority and Status as defaults for now
What you should see: Required fields show values with dynamic content tokens properly inserted.
Common mistake — Team and List IDs are long numeric strings, not the readable names you see in ClickUp's interface.
7

Create Task > Description field

Map message content to task description

Click in the Description field and select 'Text' from the Slack dynamic content. This pulls the full message text that someone reacted to. You can add context by prefixing with static text like 'From Slack channel: ' followed by the Channel dynamic field, then a line break, then the message Text.

  1. 1Click in the Description field
  2. 2Type 'From Slack channel: ' as static text
  3. 3Add 'Channel' from dynamic content
  4. 4Press Enter for a line break
  5. 5Add 'Text' from dynamic content for the message
What you should see: Description field shows formatted content mixing static text with dynamic Slack data.
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.

Use this expression in the Due Date field to set deadlines based on which channel the request came from. Paste it in the Due Date field of your ClickUp task creation step.

JavaScript — Code Stepif(
▸ Show code
if(
  contains(triggerBody()?['channel'], 'urgent'),
  addDays(utcNow(), 1),

... expand to see full code

if(
  contains(triggerBody()?['channel'], 'urgent'),
  addDays(utcNow(), 1),
  if(
    contains(triggerBody()?['channel'], 'support'),
    addDays(utcNow(), 3),
    addDays(utcNow(), 7)
  )
)
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
8

Create Task > Additional fields

Set assignee and due date

In the Assignees field, you can either hardcode a ClickUp user ID or leave it blank to create unassigned tasks. For Due Date, you can leave it empty or set a relative date using expressions like addDays(utcNow(), 7) for one week from creation. Tags can be set to help categorize these Slack-originated tasks.

  1. 1Leave Assignees blank or enter a specific ClickUp user ID
  2. 2Set Due Date to addDays(utcNow(), 7) for 7 days out
  3. 3Add 'slack-request' as a Tag for filtering
  4. 4Click Save
What you should see: Task creation action shows all fields configured with appropriate values or expressions.
Common mistake — ClickUp user IDs for assignees are numeric, not email addresses or usernames.
9

Yes branch > Add an action > Slack

Add Slack confirmation message

Add another action in the Yes branch to confirm task creation back in Slack. Search for Slack again and choose 'Post message' action. Set the Channel to the same channel where the reaction happened using dynamic content. Create a message like 'Task created: ' plus the task URL or name from ClickUp response.

  1. 1Click 'Add an action' below the ClickUp step
  2. 2Search for Slack and select 'Post message'
  3. 3Set Channel to 'Channel' from dynamic content
  4. 4Type message: 'Task created from your request!'
  5. 5Add ClickUp task URL from Create Task response
What you should see: Slack post message action configured to send confirmation with task details.
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
10

Flow designer > Save > Test

Test the complete flow

Save your flow and turn it on using the toggle in the top right. Go to your Slack workspace and react to any message with the emoji you configured (like 📝). Check that the flow runs successfully in the run history, and verify the task appears in ClickUp with the message content as description.

  1. 1Click Save in the top toolbar
  2. 2Toggle the flow to 'On'
  3. 3Go to Slack and react to a message with your emoji
  4. 4Return to Power Automate and check Run history
  5. 5Verify task created in ClickUp
What you should see: Flow shows successful run with green checkmarks, and new task visible in ClickUp.
Common mistake — First runs can take 2-3 minutes to trigger. Don't test multiple times rapidly or you'll create duplicate tasks.
Power Automate
▶ Test flow
executed
ClickUp
Slack
Slack
🔔 notification
received

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 Microsoft Power Automate for this if you're already in the Microsoft ecosystem or need the built-in integration with Teams alongside Slack. The condition logic works well for filtering specific emoji reactions, and the expression builder handles dynamic due dates better than Zapier's formatter. Skip Power Automate if you need complex message parsing or want to avoid Microsoft's per-user licensing model.

Cost

Real costs add up fast. Each emoji reaction triggers one flow run. At 50 reactions per day, you'll hit 1,500 runs monthly, which fits the free tier's 2,000 run limit. Scale to 100 reactions daily and you'll need a paid plan at $15/user/month. Zapier costs $20/month for the same volume but includes more features. Make handles this cheaper at $9/month with better debugging tools.

Tradeoffs

Make beats Power Automate on error handling - you can see exactly where flows break and retry individual steps. Zapier's Slack integration includes message threading and reaction removal triggers that Power Automate lacks. n8n gives you full control over the ClickUp API and can batch multiple reactions into single tasks. Pipedream offers superior debugging with console logs and request inspection. But Power Automate wins if you need SharePoint integration or want flows managed centrally by IT teams.

You'll hit these issues after going live. ClickUp's API occasionally returns different task ID formats, breaking URL construction in confirmation messages. Slack's emoji names don't always match what you expect - custom workspace emojis use different naming conventions. Power Automate's condition editor struggles with complex emoji filtering, so you'll end up with multiple simple flows instead of one smart flow. The 2-minute delay between reaction and task creation frustrates users expecting instant results.

Ideas for what to build next

  • Add task assignment logicRoute tasks to specific ClickUp users based on Slack channel or message content keywords.
  • Create digest workflowSend weekly summaries of tasks created from Slack reactions to track team usage patterns.
  • Build reverse notificationPost back to Slack when ClickUp tasks change status, creating a feedback loop for requesters.

Related guides

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