The idea is:
When a user uses a workflow agent via chathub, their user metadata (ie. id, firstname etc) should be included in the chat trigger payload. This is existing behaviour which is seen when publicly available chats use n8n User auth.
Publicly Available Chat
Chathub
My use case:
In many workflows, it can be useful to identify a user for session management, data security and preferences. In my particular use case, it is for internal observability purposes.
I think it would be beneficial to add this because:
Chathub workflow agent sessions may be multiuser and o forwarding user identity would allow the ability to better manage group interactions.
Any resources to support this?
None.
Are you willing to work on this?
Nay.