Why is the <code>content-type</code> header not being updated in the HTTP request sent from Webflow Logic, despite the proper configuration?
TL;DR
- Verify Webflow Logic request settings and ensure
Content-Typeis correctly included. - Use correct header formatting and check API compatibility for custom headers.
- Ensure the payload format matches the specified
Content-Type. - Remove conflicting headers if Webflow is auto-setting
Content-Type. - Debug using Webflow Logic Run History and inspect actual headers sent.
- Test with an external request inspector if necessary to check Webflow’s behavior.
If the Content-Type header is not updating in the HTTP request sent from Webflow Logic, ensure that everything is correctly configured with the following steps.
1. Check Webflow Logic API Request Settings
- Go to Webflow Logic and open the specific HTTP Request step.
- Verify that the header section includes
Content-Typewith the correct value (e.g.,application/jsonorapplication/x-www-form-urlencoded). - If using a dynamic value, ensure it resolves correctly (test with a static value first).
2. Ensure Proper Header Formatting
- Some APIs require specific capitalization (
Content-Typevscontent-type), but HTTP headers are case-insensitive by standard. - Try using
Content-Typeexactly as shown.
3. Confirm API Endpoint Compatibility
- Some APIs override or ignore custom headers, especially if they enforce a specific format.
- Check the endpoint’s documentation or try a request using Postman or cURL to see if the
Content-Typeis being modified.
4. Use the Correct Payload Format
- If sending a JSON payload, ensure:
- The
Content-Typeis explicitly set toapplication/json. - The body is formatted as valid JSON (e.g.,
{"key": "value"}). - If sending form data, use
application/x-www-form-urlencoded.
5. Remove Conflicting Headers or Auto-Formatting
- Webflow may automatically set
Content-Typewhen certain request body types are used. - Try omitting the
Content-Typeheader and see if Webflow assigns it automatically.
6. Debug with Webflow Logic Run History
- Check the Run History in Webflow Logic.
- Expand the HTTP Request step to inspect the actual headers sent.
- Compare it with what was expected and adjust accordingly.
7. Use an External Proxy for Testing
- If Webflow is modifying the headers, try sending the request to a request inspector like:
- Webhook.site
- ReqBin
Summary
If Webflow Logic is not updating the Content-Type header, verify the header configuration, try sending a static value, ensure the payload matches the expected format, and debug using Run History or an external testing service. If Webflow auto-handles the header, try removing the manual value and letting Webflow set it dynamically.