https://retellai.com/?utm_source=discord&utm_medium=seo logo
is there any way to store meta date to not be ment...
# ❓・ai-evy-support
k
@AI Evy is there any way to store meta date to not be mention in the call, aside from using dynamic variables?
a
Thanks for tagging me @K Rudy. I'll look through relevant sources and get back to you shortly.
### Answer Based on the available documentation, dynamic variables are the primary mechanism for passing context and metadata to agents in Retell AI. [(1) ]() However, there is a metadata event feature available for Custom LLM implementations that allows you to pass data from your backend to the frontend during a call. [(2) ]() This metadata event can be used to transmit information without it being mentioned in the conversation itself. For standard agent configurations (non-Custom LLM) , the sources don't explicitly describe alternative methods for storing metadata that won't be mentioned in calls beyond dynamic variables. Dynamic variables can be used in prompts, tool configurations, and other settings, but they're designed to provide context to the agent. [(1) ]() If you need more specific guidance on storing metadata silently for your particular use case, I'd recommend: - Visit [Documentation]() - Visit [Hire certified Retell partner]() Would you like a general answer based on my knowledge instead?
​ To learn more, see the sources I considered: [[1] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) [[2] Platform Changelogs | Retell AI](https://www.retellai.com/changelog) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
k
@AI Evy yes
a
Thanks for the follow-up, @K Rudy. I'll get back to you soon.
### Answer --- Based on the available sources, there is a metadata object that you can use to store arbitrary information for storage purposes only, which is not used for processing during calls. [(1) ]() [(2) ]() When creating calls via API, you can include a metadata object like this:
Copy code
json
{
  "metadata": {}
}
[(1) ]() The documentation explicitly states: "An arbitrary object for storage purpose only. You can put anything here like your internal customer id associated with the call. Not used for processing. You can later get this field from the call object." This metadata field allows you to store information that won't be mentioned or used during the call itself. You can retrieve it later from the call object when needed. **Important security note from the sources**: Both dynamic variables (
dv
) and metadata values are stored in plaintext with every call record, so avoid placing sensitive credentials or long-lived API keys in either field. [(3) ]() [(4) ]()
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.