Chat Trigger Node should pass HTTP headers to workflow

Feature Requests
1

The idea is:

Regular Webhook Trigger Nodes pass all of the headers and other information from the HTTP request to its output. Chat Trigger Node should also pass this information along.

My use case:

Things like OIDC ID Tokens and other information could be passed to the workflow in non-embedded chats

I think it would be beneficial to add this because:

This would allow for more configurable and advanced authentication of users and metadata passing to workflows using the Chat Trigger Node

Any resources to support this?

N/A

Are you willing to work on this?

If the n8n development team is engaged with our team on it, yes.