Go ahead and add us to the list.

Hi @GoFocalShift 

I’ve added you to the list of affected users, and we’ll  notify you via email once an update is readily available. Thanks.

It has been 6 months and the issue is still present. Can there be an update posted to this article? @christina.d 

Hi there! I have faced the same issue while creating a zap. What is the solution for that?

@christina.d and @jammer.solijon - I too am impacted. This is a slightly different use issue but likely originating from the same underlying matter: we have a document generation service that is trying to update a particular clickup card after the document is generated and is attempting to push the document to the clickup card. When testing, we get the same exact error message. 

Please add me to the list for when this issue is to be resolved. It appears that this matter has been going on for the last 6 months. It creates an unnecessary issue that many companies and small business owners are now having to find inefficient workarounds to resolve their situation.  

It would be helpful if you gave this extensive thread an update on the matter regardless of its completion date as this issue has persisted long enough and I imagine others will seek to either move on from clickup and/or zapier given that several alternative solutions exist.

Same issue trying to set up a zap for a new task to generate a chat in chatgpt and then send a new prompt to chatgpt using the task name to then generate an output into click up comments.

Hey ya’ll thanks for letting us know. I’ve added everyone to this bug. I’m sorry to say, we still don’t have an update or ETA.

That said, in the interest of full transparency, this app is owned and maintained by our partners at ClickUp. We’re happy to along pass your feedback and continue to collect impacted users but ultimately when a fix will be available isn’t determined by Zapier. I might recommend reaching out to ClickUp directly to share your feedback - sometimes hearing directly from their users carries more weight.

It was mentioned a bit higher in the thread but there’s also a workaround that was mentioned here that might be worth giving a shot:

We’ll be sure to pass along any updates we may here on our end but in the interim, thank you for sharing your candid thoughts with us!

Hi any update on this?
Is there a workaround? Can you add me to the list of subscribers please? 

Thanks.

@christina.d Please also add me to the list of affected users.

I have reached out to ClickUp and they have opened a ticket: CLK-254923 which you can track on their website. No word of when it will be fixed, I’m not even sure if they know.

This isn’t an issue with Zapier, it’s an API issue which is caused when GET request is sent to retrieve a task by an ID.

@ainsleydev Do you have a URL to the open ticket where I can check the status of this or should we just use this number when submitting our own ticket?

Thanks

@ChaseFromDropified 

 

We are also receiving the same error whenever we try to attach a file to a task that matches our file name. It finds the task but when the attach file step runs it is returning the “Team not authorized” error.

Can you please add me to the email list as well?

@christina.d 

im having this issue as well do we have a solution yet?

I’m getting this same error. It looks like it’s been a year since this was first mentioned here, do we have any updates?