#Twilio webhook - agent overrid
native meteor
Issue [CAI-115](https://linear.app/elevenlabs/issue/CAI-115/agent-overrides-webh...
@lusty kettle How do we get access to that spec?
lusty kettle
It's not yet developed haha. The linear ticket is our internal tool to track Feature Requests 🙂
native meteor
What sort of override? I'm familiar with the run time override, but you have to call the webhook first to get the overrides. And there's only one webhook. If that backlog item refers to allowing the specification of the two webhooks at the agent level then yes, that would help. (And then, maybe a three-tiered hierarchy of Workspace, Workgroup, Agent) so I can set up webhooks for three "classes" of agents - development, staged and published - for each workgroup and not have to specify them individually for hundreds of agents.
lusty kettle
Yes, exactly. Great.
Yeah we may do something like workgroup/projects in the future. For nowo workspace / agent it is : )
exotic vapor
an agent override would be great so we can manage different envs
lusty kettle
Coming soon!
native meteor
👆 Here's a workaround. It would be great if we could get a way of doing this natively. I'm sending an array of slots to the LLM. These slots are presented to the caller and the caller will choose one. In order to book the appointment, the easiest way to communicate this back to me is to simply send the selected slot to my booking webhook. I initially thought the Object datatype would accommodate this, but I saw that this was not the case. That datatype is used to describe a nested object, but I specifically don't want to describe the object. Just send me back the whole object. I kow what it looks like on my application layer. You can see how I worked around the issue. I'm asking for the stringified slot, which I then reconstitute to json by parsing it on the server. It works. Still, it's not the cleanest way to do this. I'd simply like to ask the LLM to send me back the slot. It seems as though that would be more robust.
Can we get the ability to inject dynamic variables into our tool urls? e.g. {{base_url}}/schedule. That way, we can have the same agent deployed for multiple systems, the url of the tools would be resolved at runtime, depending on the number the call comes in on.
lusty kettle
Can we get the ability to inject dynamic variables into our tool urls? e.g. **{{...
Interesting!
native meteor
Uploading a Word document to the Knowledgebase is broken right now. About a half hour ago it uploaded but the kname of the KB document was listed as "Unknown". Now I'm clicking Create document and nothing is happening.
Is this 21 MB limitation per document? Or for the entire account? If I'm developing agents for dozens of clients, my total knowledgebase across all my clients is limited to 21 MB? If the latter, I guess I could get around that by setting up my own KB repository (essentially text files) and simply creating links to all the documents. But it's going to be kind of messy having all these links for disparate clients co-mingled in a single KB listing for the entire account. Is there any consideration for a two-tiered KB structure? Common documents within the account KB, with agent specific KB info defined within the Agent?