Error 400 when replicating ClickUp connector in cloud environment

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

The user is facing an error 400 when trying to replicate a custom ClickUp connector in a cloud environment. The first two streams are working fine, but the third one, which involves Tasks calling a Folderless list stream, is not working.


Question

Hi team,
Trying to develop a custom ClickUp connector.
I’ve set it up on my local environment and it works, but when replicating it the in the cloud environment, I have a error 400.
I have 3 streams in my connector, the first 2 ones are working, the last one does not.
• 1st one : Spaces is alright
• 2nd one : Folderless list call Spaces stream with a parent stream, and it work
• 3rd one : Tasks calls Folderless list stream, this one does not work
Any idea about what could happen ?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["error-400", "clickup-connector", "cloud-environment", "streams", "tasks", "folderless-list"]
2

Note to us: the 400 bad request here is not about the ClickUp API, it’s about how Airbyte internally invoked the connector — seems like there’s a bug.

So you’re saying that it works in your Connector Builder running locally (all three streams), but does not work in cloud (3rd nested stream), with absolutely the same matching YAML that you copy and pasted, same value of user inputs?

If that’s the case, than it means that we’ve rolled out something in the low-code CDK that breaks the behavior you need. Check again now, if it was a bug we noticed, might be fixed already. If not:
• Please send me the yaml manifest file, I will try it on Cloud
• Lookup the version of your local builder — what version tag does it have?

3

No I havent set it up by importing YAML (didn’t think about it actually) but I just set up things exactly in the same way.
I have change the parent stream so there is less entries and now it works so I assume it was because of it

4

Try copy and pasting the actual yaml — that would ensure they’re actually absolutely identical.