ClickUp - Create a task

Use the ClickUp - Create a task action A tool for building the processes, logic, and direction within workflows. Actions are the steps the workflow performs to complete a process. to create a new task in ClickUp.

For more information about ClickUp, go to ClickUp.

Before you begin: 

Jump to:

Configure the ClickUp - Create a task action

  1. Add the action to the workflow and open the action configuration panel. For more information, see Add an action to the workflow.

  1. Select a Connection. If you do not have a connection, see Add a connection.
  1. If you already have a list ID in a workflow variable, insert that variable in the List field. If you don't have the list ID then follow these steps to retrieve the lists from your ClickUp connection:
    1. Select the Team where the task will be created.
    2. Select the Space where the task list's folder is located.
    3. Select the Folder.
    4. Select the List where the task will be created.

  2. Specify a Name for the task.

  3. Add a description, assignees, tags, task status, priority, due and start dates, a time estimate, and if all the assignees are notified.

  4. Create or select a variable for the output.

ClickUp - Create a task action fields and settings

Section

Field

Description

Variable types

(Unlabeled)

Connection Credentials and other settings that enables workflows to communicate with external systems, services, or applications. It's required to pass data between the workflow and the indicated service, which could be a cloud service, business application, or content store.

The ClickUp connection to use to create a task.

To refresh the available connections, click .

(n/a)
  Team

The ClickUp team where the task will be created. This drop-down populates with the list of teams once the connection is made.

 Text, Decimal, Integer, Boolean, DateTime, Collection
  Space The ClickUp space where the task will be created. This drop-down populates with the list of team spaces once the Team field is selected. Text, Decimal, Integer, Boolean, DateTime, Collection
  Folder The ClickUp folder where the task will be created. This drop-down populates with the list of folders once the Space field is selected. Text, Decimal, Integer, Boolean, DateTime, Collection
  List

The ClickUp list where the task will be created. This drop-down populates with the list names once the Folder field is selected.

You can use the list ID from a previous Create a task action or from a previousClickUp - Update a task action.
 Text, Decimal, Integer, Boolean, DateTime, Collection
  Name

The name of the task you are creating.

 Text, Decimal, Integer, Boolean, DateTime, Collection
  Description

A description for the task you are creating.

 Text, Decimal, Integer, Boolean, DateTime, Collection
  Assignees

Team members to assign this task to. Click Add assignee to add a member to the assignees list.

You can use the assignee ID from a previous Create a task action or from a previous ClickUp - Update a task action.
 Integer
  Tags Custom tags to help organize your tasks. Click Add tag to create a new tag for this new task. Text, Decimal, Integer, Boolean, DateTime, Collection
  Status The status of the new task. This drop-down populates when you select the ClickUp Space. Text, Decimal, Integer, Boolean, DateTime, Collection
  Priority The priority of the new task: Urgent, High, Normal, or Low. Integer
  Due date

The date, in Unix time (including milliseconds), that this task will be completed.

Unix time (also known as Epoch time, Posix time, seconds since the Epoch, or UNIX Epoch time) is a system for describing a point in time. It is the number of seconds that have elapsed since the Unix epoch, minus leap seconds; the Unix epoch is 00:00:00 UTC on 1 January 1970 (an arbitrary date); leap seconds are ignored, with a leap second having the same Unix time as the second before it, and every day is treated as if it contains exactly 86400 seconds. Unix time is widely used in operating systems and file formats.

The following steps present an example of how to get Unix time from a date in a form input:

  1. In a form, create aDate/time picker control called Target Date.

  2. Add a variable that calculates the TotalSeconds between 1970/1/1 00:00:00 and your target date:

    • dateDiff("TotalSecond", date(1970,1,1,0,0,0), Form.Target Date)
      Unix time

  3. Test the form to make sure that the control is working. For example, selecting 12pm on the 9th of June 2021 should result in a Unix time of 1623240000.

 Integer
  Display due date/time Select whether to display the time with the date, or just the date, on the ClickUp site. Boolean
  Start date

The date, in Unix time (including milliseconds), that this task is to start on.

Unix time (also known as Epoch time, Posix time, seconds since the Epoch, or UNIX Epoch time) is a system for describing a point in time. It is the number of seconds that have elapsed since the Unix epoch, minus leap seconds; the Unix epoch is 00:00:00 UTC on 1 January 1970 (an arbitrary date); leap seconds are ignored, with a leap second having the same Unix time as the second before it, and every day is treated as if it contains exactly 86400 seconds. Unix time is widely used in operating systems and file formats.

The following steps present an example of how to get Unix time from a date in a form input:

  1. In a form, create aDate/time picker control called Target Date.

  2. Add a variable that calculates the TotalSeconds between 1970/1/1 00:00:00 and your target date:

    • dateDiff("TotalSecond", date(1970,1,1,0,0,0), Form.Target Date)
      Unix time

  3. Test the form to make sure that the control is working. For example, selecting 12pm on the 9th of June 2021 should result in a Unix time of 1623240000.

  
  Display start date/time Select whether to display the time with the date, or just the date, on the ClickUp site. Boolean
  Time estimate An estimated time to complete this new task. Integer
  Notify all assignees Select whether to send task creation notifications to everyone including the creator of the task. Boolean
Output Task Stores the result of the action as an object. The following values are returned:
  • Archived: (Boolean) Whether or not the task is archived.
  • Assignees: (Collection) List of users assigned to the task:
    • Color: (Text) User's color definition.
    • Email: (Text) User's email address.
    • ID: (Integer) User's unique identity number.
    • Initials: (Text) User's initials.
    • Profile picture URL: (Text) Link to the user's profile picture.
    • User name: (Text) The user's name.
  • Creator: (Object) Details of the task creator:
    • Color: (Text) Task creator's color definition.
    • Email: (Text) Task creator's email address.
    • ID: (Integer) Task creator's unique identity number.
    • Initials: (Text) Task creator's initials.
    • Profile picture URL: (Text) Link to the task creator's profile picture.
    • User name: (Text) The task creator's name.
  • Date closed: (Integer) The date the task was closed (typically null for a new task). In Unix time.
  • Date created: (Integer) The date the task was created. In Unix time.
  • Dependencies: (Collection) List of tasks that depend on the completion of this task.
    • Date created: (integer) The date the dependency was added. In Unix time.
    • Depends on: (Text) The task dependency link.
    • Task ID: (Text) The dependent task's identifying number.
    • Type: (Integer) The type of dependency, such as blocking, or waiting on.
    • User ID: (Text) This variable returns a value from the API for use throughout the workflow.
  • Due date: (Integer) The date this task is due to be completed on.
  • Folder: (Object) Details of the folder this task is created in:
    • Access: (Boolean) If the folder is open or closed for access.
    • Hidden: (Boolean) Whether the folder is hidden or not.
    • ID: Text) The unique identifier of the folder.
    • Name: (Text) The name of the folder.
  • ID (Text) The unique identifier of the task.
  • List: (Object) Details of the task list:
    • Access: (Boolean) If the task list is open or closed for access.
    • ID: Text) The unique identifier for the task list.
    • Name: (Text) The name of the task list.
  • Name: (Text) The name of the task.
  • Order index: (Text) The position that this task will show in.
  • Permission level: (Text) The permission level needed to access this task.
  • Project: (Object) Details of the project this task is created in:
    • Access: (Boolean) If the project is open or closed for access.
    • Hidden: (Boolean) Whether or not the project is hidden.
    • ID: Text) The unique identifier of the project.
    • Name: (Text) The name of the project.
  • Space: (Object) Details of the space that the task is created in.
    • ID: (Text) The unique identifier of the space.
  • Start date: (Integer) The starting date for the task.
  • Status: (Object) Details of the status assigned to the task.
    • Color: (Text) The color of the status.
    • Order index: (Text) The position that this status will show in, zero based.
    • Status: (Text) Whether the status is open, in progress, closed, or a custom status.
    • Type: (Text) The status type.
  • Tags: (Collection) List of tags assigned to the task.
  • Team ID: (Text) The unique identifier of the team.
  • Time estimate: (Integer) An estimated time to complete the task. In Unix time.
  • URL: (Text) The ClickUp URL to the task definition.
  • Watchers: (Collection) List of users with access to observe the task details:
    • Color: (Text) User's color definition.
    • Email: (Text) User's email address.
    • ID: (Integer) User's unique identity number.
    • Initials: (Text) User's initials.
    • Profile picture URL: (Text) Link to the user's profile picture.
    • User name: (Text) The user's name.
 Object