Thanks for the feedback! We recently rolled out a multithreading logic to increase sync speeds. Based on the feedback from you and other customers, we are going to make multithreading optional on the Zendesk setup form.

Has there been any update on this? We are experiencing the exact same issue.

Support told us that Fivetran will use 90% of the quota, whatever it's set to.  Please give us a way to lower that.

+1 to this one - our Fivetran connector is using 90% of our quota Zendesk which causes rate limiting for the active customer traffic using our Zendesk throughput. Can you provide any updates on this? 

Another +1 to add a cap setting. We recently had a production incident caused by hitting our API limit, and we've determined that the Fivetran sync is the primary consumer.

Another +1 to this.

Relying on the API is not a satisfactory solution. Without visibility in the UI, our admins cannot manage the connections effectively - we don't expect everyone to know how to interact with a REST API!

Also, if the connection was ever removed and re-created for any reason, we would not know the previous setting unless we manually documented it somewhere. Distributing processes and configurations across multiple sources is not a good way to manage our infrastructure. Fivetran is supposed to be a single entry point and a single source of truth for our integrations.

Finally, we don't want a hybrid where the UI manages most connections, but an API manages a subset. What's the point of paying for a third-party service to handle our integrations if we have to configure things manually using an API? We might as well write the whole thing.

Other connections have many more config settings than the Zendesk one, so we don't understand why you cannot add a simple setting to the connection setup to specify the usage with the existing default value preset.