Skip to main content

I’m building a Zap that connects ClickUp to ClickUp and automates the following workflow:

1. Trigger: When a specific tag is added to a task in ClickUp (✅ already set up).

2. Action 1: Create a new folder using a folder template in a specific space (✅ already working).

3. Action 2 (Problem Area): After the folder is created, I want to update a custom field on the original task where the tag was added.

 

I’m currently stuck at Step 3 — trying to update the custom field on the original task, but I’m not sure how to correctly pull in that Task ID into the action, even though I was told that this could be done using the “field mapping” option.

 

 

In the screenshot I attached:

• The Zap is trying to pull a Task ID to apply the custom field update, but I don’t see the original task’s ID (the one where the tag was added) appearing in the Create Folder step’s output.

• I’m wondering why the task ID is not available in the “Create Folder” step, and how I can correctly reference the original task (from the first step) here. I’m using field mapping but the task IDs provided belong to current tasks, so I don’t want to use those IDs as the default ones to update the custom field of the new task.

 

How can I pass the Task ID from the first step (where the tag is added) into the final action that updates the custom field?

Hi ​@Justin Coats 

You need to map the ID of the Task from Zap step 1.

Search for ID to narrow the results of variables to select.

 


I look for “ID” in the search box, but it only gives me a task ID that already exists under another folder in ClickUp. I’m using that one to see if it works. 

 

But now i’m getting an error when I look for the Task custom field ID. This is how i’m looking for the ID:

 

 

But it has a lot of custom fields IDs in one. I can’t find the right custom field in the first step.

 

“The error message I get when I select this option is:

The error message "Field is must be a valid UUID" indicates that the value provided for a field expected to be a UUID (Universally Unique Identifier) is not in the correct format. In your input data, the field "custom_field":"{{291160902__task__custom_fields_]id}}" seems to be the culprit. The placeholder {{291160902__task__custom_fields2]id}} is likely not resolving to a valid UUID, which is a 36-character string including hyphens, such as 123e4567-e89b-12d3-a456-426614174000.

To resolve this issue, first ensure that the custom_field value is correctly mapped to a valid UUID. You can do this by checking the output of the previous step to confirm that the custom_field ID is being correctly captured and formatted. If the previous step does not provide a valid UUID, you may need to adjust the data mapping or use a Formatter step in Zapier to transform the data into the correct format. Additionally, verify that the custom field you are trying to update exists and is correctly configured in ClickUp. If necessary, manually input a valid UUID to test if the issue is with the dynamic data.”

 

Since the previous step doesn’t provide a valid UUID, how can I adjust the data mapping or use a Formatter step in Zapier to transform the data into the correct format?


@Justin Coats 
You likely need to use the ClickUp API to get the individual custom field internal id.

Then you can set a hardcoded value for the Zap step field.
 

Option: Use the Public API to List Custom Fields

  1. Go to ClickUp API:
    https://developer.clickup.com/reference/getteamavailablefields

  2. Use the endpoint:
    GET /list/{list_id}/field
    or
    GET /space/{space_id}/custom_field

  3. This returns all custom fields with their internal id, name, type, etc.

 

 


Hi ​@Justin Coats,
 
We just wanted to see how everything is going with your Zap. Did Troy's recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
 
We're looking forward to your response.