Why is the <code>content-type</code> header not being updated in the HTTP request sent from Webflow Logic, despite the proper configuration?

If the Content-Type header is not being updated in a Webflow Logic HTTP request, it's usually due to how Webflow Logic handles custom headers and body formats internally, especially with JSON payloads.

1. Webflow Logic Auto-Sets Content-Type

• Webflow Logic automatically sets Content-Type based on the selected request body format.
• If you specify a body as JSON, Webflow sets Content-Type: application/json by default. Manually overriding it often won't take effect.
• Similarly, for Form-encoded bodies, Webflow will set application/x-www-form-urlencoded.

2. Manual Overrides Are Restricted

• Webflow does not currently allow full manual control over request headers in Logic flows.
• Any attempt to add a custom Content-Type header to override the default is typically ignored.

3. Workaround for Custom Content-Types

• If you need a non-default Content-Type (e.g., application/xml), standard Webflow Logic HTTP blocks do not support this directly as of now.
• Possible workarounds:
• Use an external webhook service like Make, Zapier, or a custom serverless function to receive the Logic data and forward it with modified headers.
• You may pass raw text in the body and configure your external service to interpret it accordingly.

4. Check for Webflow Limitations

• As of 2024, Webflow Logic has:
• No advanced header configuration support.
• No full raw request mode (like Postman's "Raw" or custom Curl-level format).
• Always consult the Webflow Logic Docs for current platform limitations.

Summary

Webflow Logic auto-sets the Content-Type header based on the body format and does not allow manual overrides. To use a different header, route your call through an external service that can fully customize HTTP requests.