Description
Currently, when submitting forms in n8n, only the form parameters are passed along, and request headers are not included. This limits the ability to use additional metadata that might be present in the headers.
Use Case
There are cases where request headers contain important information that needs to be used in workflows. For example:
- User Authentication: A reverse proxy like Caddy can pass the authenticated user’s email in a header. Without access to headers, this information cannot be used in the workflow.
- API Integrations: Some external services send critical request context in headers, such as authorization tokens, custom metadata, or tracing information.
Proposed Solution
When a form is submitted, allow n8n to capture and pass along request headers along with form parameters. This could be an opt-in feature in the node settings to avoid unintended data exposure.