14

Workflows

Last Update 2 giorni fa

Getting started with Workflows Creating your first workflow, step by step Choosing what triggers a workflow Building workflow steps: actions, conditions, waits and AI steps Using runtime data in workflows

Creating ClickUp tasks with workflows

Does your team manage its work in ClickUp? A workflow can create a ClickUp task, for example when a visitor asks your AI agent for a call-back.

tawk.to has no ClickUp step, so you connect the two yourself. In ClickUp, you create an API token. In tawk.to, an HTTP request step uses it to create each task. You copy a token, a List ID and a short template, and you do not write code.

Time: about 20 minutes.

What you can and cannot do
You canCreate a task in a ClickUp List, with a name, a description and a priority.
You cannotEasily assign the task to a person: ClickUp needs their user ID, which the ClickUp app does not show. Set a due date from words like "tomorrow at 3 pm": ClickUp needs a date in a machine format. Put the visitor's name, email address or chat messages straight into the task: they must come from your AI agent or an AI step (see What you can put in the task below).
You needThe property admin role in tawk.to, and a ClickUp account with access to the List for your tasks.
Tasks are created in the name of the person who owns the token.

Tip: To give each task an owner, add an automation in ClickUp, for example "When a task is created, assign it to…".

Step 1: Create a ClickUp API token

  1. In ClickUp, click your avatar in the top-right corner.
  2. Click Settings.
  3. Click Apps.
  4. Under API Token, click Generate.
  5. Click Copy. The token starts with pk_.
Important: The token can open everything that its owner can see in ClickUp. Keep it private.

If the token's owner leaves your company, the workflow stops working. Use the account of someone who will stay, or a shared account.

For more, see ClickUp's guide Authentication.

Step 2: Find the List ID

  1. In ClickUp, open the List for your tasks.
  2. Look at the address in your browser. The List ID is the number after /li/.

Step 3: Add an HTTP request step in tawk.to

  1. Open your workflow in Automations > Workflows.
  2. Click Add step.
  3. Click Action.
  4. In Category, select Developer tools.
  5. In Action, select HTTP request.
  6. In URL, type https://api.clickup.com/api/v2/list/YOUR-LIST-ID/task.
  7. Replace YOUR-LIST-ID with the ID from step 2.
  8. In Method, select POST.
  9. Under Headers, click Add header and fill in the header from the table below.
  10. In JSON body, paste the template below.
  11. Click Save.
Header nameHeader valueSecret
AuthorizationYour API token, for example pk_123…On
Type only the token. Unlike some other tools, ClickUp does not want the word Bearer before it.

Turning on Secret hides the token after you save. tawk.to sends secret headers only to https:// addresses.
In the template, priority is a number: 1 is Urgent, 2 is High, 3 is Normal and 4 is Low. \n starts a new line in the description.

Note: The JSON body must be valid JSON, or you cannot save the step. Keep each {{ }} value inside quotation marks, as in the template. tawk.to inserts the details safely, even when they contain quotation marks or line breaks.

What you can put in the task

Workflow starts fromWhat you can useExample
Your AI agent (AI agent trigger)The details that the agent collects{{trigger.name}}, {{trigger.phone}}
A chat (for example Chat transcript created)The output of an AI step that summarizes the chat{{nodes.<step ID>.output}}
A website form (Webhook trigger)The fields that your form sends{{trigger.message}}
A webhook request must be signed, so a website form usually needs a developer to send it. See Choosing what triggers a workflow.

Why chats need an AI step: the visitor's name, email address and chat messages are private details. An HTTP request cannot send them, because only Slack steps and conditions can use them. An AI step can read them and write a summary, which you put in the description.

The template above uses the details that the Request a call-back template collects. To build on it, add the HTTP request step to that template. If you do not also want a task in tawk.to, delete its Create activity step. For how your AI agent collects these details, see Letting your AI agent run workflows.

For every detail you can use, see Using runtime data in workflows.

Step 4: Test it

  1. In the Settings tab, turn on Enabled and click Save.
  2. Click the Runs tab.
  3. Click Run now.
  4. In Trigger data (JSON), change the sample values to a test name and phone number.
  5. Click Run now.
  6. Check your ClickUp List for the new task.
  7. Click the run to see the result.
If the step failed, ClickUp's response in the run tells you why.

Important: Run now starts a real run, so every step in the workflow runs.

If it does not work

What you seeWhat to do
Status 400The JSON body is not correct. Compare it with the template.
Status 401The token is wrong. Check that the Authorization header holds only the token, with no Bearer.
Status 404The List ID is wrong, or the token's owner cannot see the List.
By default, any status outside 200 to 299 fails the step and stops the run. If later steps should still run, turn on Continue even if the request fails in the step. Later steps can then check the HTTP status.

For more about runs and errors, see Testing, monitoring and troubleshooting workflow runs.

Good to know

  • Copies lose the token. A copy made with Duplicate does not include secret headers, so the Authorization header is gone. Add it again, with Secret on, before you turn on the copy.

Related guides

Have a question we haven't covered or need support?

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us