#What is the difference in the Conversation Initiation Client Data Webhookin https://elevenlabs.io/
1 messages · Page 1 of 1 (latest)
AI-generated Answer for trinhthiquynhanh
Short answer:
- Agents settings (workspace-level): The “Conversation initiation client data webhook” here defines the single webhook endpoint (URL + optional request headers) that ElevenAgents will call at conversation start to fetch per-conversation data (dynamic variables and optional overrides). It applies across the workspace unless your integration supplies its own source. (elevenlabs.io)
- Agent page → Security tab (per‑agent): This does not set a webhook URL. It’s where you opt‑in which fields from conversation initiation client data are allowed to override the agent at runtime (e.g., First message, System prompt, LLM/voice). Overrides are disabled by default and must be enabled here; new client‑driven fields (e.g., starting_workflow_node_id) are also gated by Security/platform override settings. (elevenlabs.io)
Supporting docs:
- Workspace settings API shows conversation_initiation_client_data_webhook object (url, request_headers). (elevenlabs.io)
- Twilio inbound calls use this webhook to return conversation initiation client data (dynamic_variables and overrides). (elevenlabs.io)
- Personalization/Overrides docs define the conversation_initiation_client_data payload and note that per‑agent Security must enable specific overrides. (elevenlabs.io)
- Changelog notes additional client-init fields are opt‑in via agent platform/Security settings. (elevenlabs.io)
Sources:
Update settings | ElevenLabs Documentation
Overrides | ElevenLabs Documentation
Update settings | ElevenLabs Documentation
Twilio personalization | ElevenLabs Documentation
Personalization | ElevenLabs Documentation
April 20, 2026 | ElevenLabs Documentation
So meaning to say that the Security tab section is thing that overrides in the overall Setting right ?