The idea is:
Being able to know who users are that interact with Form or Chat nodes.
Technically I would like to be able to access HTTP Headers of Forms and Chat nodes, similar to what a WebHook node currently provides (n8n 1.68.1)
My use case:
Self Hosted. My proxy in front of n8n (nginx / traefic / Azure Web Application Firewall) injects HTTP Request Headers like ‘authenticated-user-email’ and ‘authenticated-user-groups’ after authenticating the end user against our organization’s Azure AD (only for some URL patterns, like for Forms and Chat endpoints). I want to access this information in my workflows so that my workflow can behave differently for different users and groups. Think of Approval workflows, where we need to know who the user is before accepting a decision, or chat messages where we need to find user specific content to inject into an AI Agent’s context.
I think it would be beneficial to add this because:
Forms and Chat are only useful in internal business scenarios if we know who the end-user is.
And while I could build my own UIs using the WebHook, this takes time and is a step backwards in terms of productivity.
Any resources to support this?
Are you willing to work on this?
Yes, I am willing to contribute, although I suspect this change will have to be made in the N8N core, not a custom node.,