Yes—pass the conversation ID to your webhook tool via a dynamic variable. Use the built‑in system dynamic variable system__conversation_id. It’s available automatically and, in tool calls, it’s populated at execution time with the current conversation’s ID. (elevenlabs.io)
How to include it in a webhook (server) tool
In the tool config, add the parameter where you want the ID (header, query, path, or body) and set its value type to Dynamic variable, selecting system__conversation_id. You can also reference it inline in tool parameter strings using {{system__conversation_id}}. (elevenlabs.io)
If you need it in the URL path, declare a path placeholder (e.g., /api/events/{conversation_id}) and map that path parameter to the system__conversation_id variable. (elevenlabs.io)
How to know the exact value at runtime
The platform supplies the value; you don’t need to compute it. If you’re connected over WebSocket, the conversation_id is also sent in the conversation_initiation_metadata event, so you can capture/log the literal string your agent is using. (elevenlabs.io)
If you start sessions via the React SDK, startSession resolves to a conversationId you can store and, if desired, mirror into your webhook as well. (elevenlabs.io)
Notes
system__conversation_id is one of the documented system dynamic variables; system variables are available without extra setup and are updated for tool calls during an active conversation. (elevenlabs.io)
Tool schemas support dynamic variables for headers, query/body/path params; see the server tools guide and example tool JSON structure. (elevenlabs.io)
wanton bough
pallid creek