Custom Endpoint providing dynamic data like "conversationId" from librechat

[schnaker85]

hi danny,

is there a way to add a "dynamic" parameter like the conversationId from librechat to a custom Endpoint request object/header?

I checked https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/custom_endpoint#addparams and headers but do not support this as far as I understood.

The use case we would like to tackle is the following: We would like to know what original conversation the message(s) came from, to be able to store the messages in the custom endpoint backend in the original conversation. (outside of librechat)

Thanks for the help!

cheers
dani

[yaszin]

Any updates on this?

[MartyWind]

I find this interesting, too, as I am trying to connect dify.ai to LibreChat. It worked like a charm to connect a dify workflow via MCP but to maintain conversation history, dify requires a conversation_id that is returned in the first response from dify.

Is there a way to extract that ID from the first response and include it in subsequent requests?

[schnaker85]

it looks like this is possible with the most recent rc Release.
This PR will solve this: #9095
It will be in the next Release 0.8.0 Release 🚀
thanks @danny-avila !