Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I am trying to create a subtask based on a task changing in ClickUp. I have successfully created subtasks through other ClickUp spaces with no issues using a similar process, but this space is causing me some grief. All spaces, including the one that I am experiencing an issue with, were all created by me and it's my ClickUp account that is connected through Zapier.

The issue that I am experiencing is with setting custom fields on the task at time of subtask creation. I can set the standard ClickUp fields, like task name, task status and tags, for example, but I have been unable to set any custom field values at time of subtask creation. Fields in question are not locked down in any way and I have full editing rights within the space.

Here is what I attempted so far and am open to trying something different: 

  • Connecting a new account and trying the zap through there
  • Recreating the zap through a different workflow
  • Turning on the zap, then off again - tried running it as a test while the workflow was off and also tried triggering it to run. There is no issue with the subtask getting created, but the custom fields are not being set, even when the workflow is on
  • Set custom values initially through the “Create subtask” action, but also attempted to set static values for debugging and those static values are not appearing in the subtask either

One important note is that I can set the custom field individually after the subtask has been created through Zapier; however, there are 52 custom fields so I would prefer to set them at time of subtask creation, so it makes it easier for auditing and/or adjustments. 

Hi ​@AcquireUp 

Try turning the Zap ON and testing live, then check the Zap Run history details to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/

Check the LOGS tab to see the underlying API request/response to help you troubleshoot the actual inputs/outputs.

There may be clues there for you to use.

Hi there, ​@AcquireUp! 👋

How are things going with this? Were you able to find any clues in the Zap history as to why the custom field isn’t being populated on the subtask when it’s created?

Want to make sure this gets sorted, so please keep us posted on your progress here!

​@SamB ​@Troy Tessalone 

I can see the data coming in, especially at the create subtask step, but unfortunately, even if I set a value in a custom property as a static option from the list of drop downs, it does not feed over into the subtask creation. If I create the subtask first, I can update the record immediately after with the same values in the same workflow but I have to set the values individually per action using the custom field action

It seems to be tied to setting custom fields at time of subtask creation. I can’t set any custom fields when creating the subtask but can set them when creating a new task through the same workflow. It seems to be tied to this specific action. 

Is there a different action we should be using for this other than “Create Subtask” action to create a subtask?

Hi ​@AcquireUp,

 

If you're having trouble setting custom fields when creating a subtask in Zapier, it may be due to limitations in the app's "Create Subtask" action. A common workaround is to make the subtask first, then update it in a second step to set the custom fields. If supported, you can also use Webhooks by Zapier action to send a custom API request. Ensure your app and Zapier integration are up to date, and contact Zapier support if the issue continues for more tailored help.

If you have any more questions or need further assistance, feel free to ask. We're here to help.

Terms & Conditions