Create a task in a folder

Connector functions are a new addition to Slack automations. We recommend understanding the systems and APIs you're integrating with before setup.

Facts

Schema:	`Connectors.Clickup.functions.CreateTask`
Service:	ClickUp

Input parameters

Required parameters

clickup_access_token

slack#/types/credential/oauth2

·Required

Determines whether this connector will use the credentials of the user starting the workflow or the credentials configured by an app collaborator. See the Authentication section on this page for details.

Example

{ credential_source: "END_USER" }

team_id

integer

·Required

The ID of the team that will own this task

Example

1234

space_id

integer

·Required

The ID of the space in which this task will be created

Example

5551234

folder_id

integer

·Required

The ID of the folder in which this task will be created

Example

281330

list_id

integer

·Required

The ID of the list in which this task will be created

Example

8004

name

string

·Required

The name of the task

Example

"Build new workflow for sales channel"

Optional parameters

description

string

·Optional

A description for the task

status

string

·Optional

The status for this new task

assignees

array

·Optional

Array of ClickUp user IDs to assign this task to

start_date

slack#/types/timestamp

·Optional

The start date of the task, as a Unix timestamp

due_date

slack#/types/timestamp

·Optional

The due date of this task, as a Unix timestamp

tags

array

·Optional

An array of tag IDs from tags in the provided Space with which to tag this task

Output parameters

Required parameters

task_id

string

·Required

Task ID

task_name

string

·Required

Task name

start_date

string

·Required

Start at

due_date

string

·Required

Due at

description

string

·Required

Description

date_created

string

·Required

Created at

url

string

·Required

Link to task

Authentication

A connector's access token property specifies how the connector handles authentication.

End-user authentication

user Workflows that include a connector function relying on end-user authentication can can only be started with a link trigger.

clickup_access_token: {
    credential_source: "END_USER"
}

End-user experience: User will be prompted to link their external account via OAuth when they first start the workflow that contains this connector.

Developer experience: Developer does not have to implement authentication in app.

Developer authentication

clickup_access_token: {
    credential_source: "DEVELOPER"
}

End-user experience: User can start a workflow containing the connector (they are not prompted to authenticate).

Developer experience: One of the app's collaborators configures external authentication via the CLI before sharing the app with users.

How to use

First, import Connectors from deno-slack-hub into your project's import_map.json file, like this:

{
  "imports": {
    "deno-slack-hub/": "https://deno.land/x/deno_slack_hub@2.2.0/",
    "deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.14.2/",
    "deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/",
  }
}

Next, import Connectors at the top of your workflow's definition file:

// my_workflow_file.ts
import { Connectors } from "deno-slack-hub/mod.ts";

Finally, add the connector as a step in your workflow just like you would a built-in Slack function.

SomeWorkflow.addStep(
  Connectors.Clickup.functions.CreateTask, {
  //...

🧙🏼 Your admin may need to approve the connector first. If your workspace has been configured to only allow admin-approved apps, the CLI will prompt you to send an admin approval request the first time you try to use a connector that hasn't been approved by an admin yet. While waiting for admin approval, the CLI may report an error like this:

Workflow function... is referring to an unknown step output parameter...

You can safely ignore this error; it will go away as soon as your workspace admin approves your request to use the connector.