Create ClickUp Tasks from Slack Slash Commands

Overview

This workflow enables you to instantly create new tasks in ClickUp directly from a Slack slash command. Instead of manually switching between apps and re-typing task details, team members can simply type a command like /newTask Design the new landing page in any Slack channel, and a corresponding task will be automatically created in your designated ClickUp list. This dramatically reduces friction for capturing ideas, action items, and assignments, ensuring nothing gets lost in chat.

How It Works (Step-by-Step)

Below is a detailed breakdown of each node in the workflow and its role in the automation.

1. Receives slack command — Webhook node (No auth)
   This node creates a unique HTTP endpoint URL that you configure as the Request URL for your Slack Slash Command. It listens for incoming POST requests from Slack whenever a user types the slash command. The httpMethod is set to POST, and the responseMode is set to responseNode, meaning it will wait for a later node (the Respond to Webhook node) to send the reply back to Slack.

2. Set your nodes — Set node (No auth)
   This node extracts and re-maps key fields from the incoming Slack webhook payload. It takes the raw $json.body data and creates four clean, named output variables: channel_name, command, user_name, and text. The text field contains the actual task description typed by the user after the slash command (e.g., "Design the new landing page"). This step makes the data easier to use in subsequent nodes.

3. Create new clickup task — ClickUp node (OAuth2)
   This is the core action node. It uses the ClickUp API (authenticated via OAuth2) to create a new task. The task name is dynamically set to the value of {{ $json.text }} (the user's input). It is configured to create the task in a specific ClickUp Team (9009074051), Space (90090146907), and List (900900727522). The folderless option is set to true, meaning the task is created directly in the list rather than inside a folder. The task's content (description) is also set to the same text from the slash command.

4. Respond to Webhook — Respond to Webhook node (No auth)
   This node sends an immediate confirmation message back to the Slack channel where the command was issued. It responds with a plain text message: Task Created: ID {{ $json.id }}. The {{ $json.id }} placeholder is dynamically replaced with the ID of the newly created ClickUp task, giving the user a direct link or reference to the task.

Setup Instructions

To use this workflow, you will need the following accounts and credentials:

1. Slack Account: You need permission to create a new Slash Command in your Slack workspace. Go to your Slack API dashboard (https://api.slack.com/apps), create a new app (or use an existing one), navigate to Slash Commands, and create a new command (e.g., /newTask). Set the Request URL to the webhook URL generated by the Receives slack command node in n8n. You can find this URL by opening the node and copying the "Production URL" or "Test URL".
2. ClickUp Account: You need a ClickUp account with access to the Team, Space, and List where you want tasks to be created. You will also need to create an OAuth2 integration in n8n. In the Create new clickup task node, click on the "Create New" button next to the Credential for ClickUp dropdown and follow the OAuth2 flow to authorize n8n to access your ClickUp account.
3. n8n Instance: You need a running n8n instance (self-hosted or cloud). Import this workflow, activate it, and follow the steps above to configure the Slack endpoint and ClickUp credentials.

Use Cases and Variations

• Task Capture for Any Team: This workflow is ideal for engineering, marketing, design, or operations teams that use Slack for communication and ClickUp for project management. It turns casual conversations into trackable work items.
• Adding Assignees: You can modify the Create new clickup task node to automatically assign the task to the user who issued the command. In the additionalFields section, you could map the user_name from Slack to a ClickUp user ID (this would require a lookup table or a separate API call).
• Custom Task Fields: You can extend the workflow to set ClickUp custom fields (e.g., priority, status, due date) by adding more parameters to the additionalFields object in the ClickUp node.
• Multi-Command Support: You could add a conditional node (e.g., an IF node) to handle different slash commands differently. For example, /bug could create a task in a "Bugs" list, while /feature creates one in a "Features" list.
• Error Handling: The workflow JSON includes references to error-handler nodes, but they are not fully connected. You could add an Error Trigger node to send a notification to a Slack channel if the task creation fails.

{
  "meta": {
    "instanceId": "workflow-1a1a26d7",
    "versionId": "1.0.0",
    "createdAt": "2025-09-29T07:07:42.296535",
    "updatedAt": "2025-09-29T07:07:42.296544",
    "owner": "n8n-user",
    "license": "MIT",
    "category": "automation",
    "status": "active",
    "priority": "high",
    "environment": "production"
  },
  "nodes": [
    {
      "id": "c39381ac-4795-4408-9383-7bae62755569",
      "name": "Respond to Webhook",
      "type": "n8n-nodes-base.respondToWebhook",
      "position": [
        1580,
        640
      ],
      "parameters": {
        "options": {},
        "respondWith": "text",
        "responseBody": "=Task Created: ID  {{ $json.id }}"
      },
      "typeVersion": 1,
      "notes": "This respondToWebhook node performs automated tasks as part of the workflow."
    },
    {
      "id": "ff72f0cb-1ea2-41e5-8f9f-7aa7ce994632",
      "name": "Sticky Note",
      "type": "n8n-nodes-base.stickyNote",
      "position": [
        900,
        500
      ],
      "parameters": {
        "color": 4,
        "width": 874,
        "height": 359,
        "content": "## Create new tasks to airtable from a slack command"
      },
      "typeVersion": 1,
      "notes": "This stickyNote node performs automated tasks as part of the workflow."
    },
    {
      "id": "263f6c3b-5225-4d3f-a8ce-5052946b4251",
      "name": "Receives slack command",
// ... truncated (copy to see full JSON)