I'd like fivetran connectors to support adding custom HTTP headers or cookies for HTTPS services it syncs.

As companies move to zero-trust solutions it is going to be less common to have a raw network port open to the internet for fivetran to hit. These systems typically work transparently for browsers that can follow redirects to authentication systems, but vanilla API clients are not able to perform these sorts of transactions. Instead, API clients need to supply some authentication information in the form of an HTTP header or cookie.

The header name and value/cookie value would need to be configurable by the connector administrator. Depending on the company's policy this may need to be changed frequently (which would necessitate this being available in the fivetran UI/API directly) or they may be long lived (in which case some more janky non self-service mechanism may be acceptable.)