Webhook not receiving data from Eleven Labs

Questions
1

When I test the webhook node, and the voice agent that was created in eleven labs, the webhook does not receive any data. It did once, maybe even twice, so I pinned the data and continued with the workflow. When I unpinned the data and executed the workflow, the initial webhook is no longer receiving the data. I’ve started over a few times, but the voice agent is not passing any data. This is probably an issue with my eleven labs config., but maybe someone has experienced this and can offer some advice? Thanks

Both the webhook and voice agent are set to post.
The voice agent has all permissions.
Eleven labs credentials are good.
I am copy and pasting the webhook url in voice agent.
Disabled firewall.

Please share your workflow: Just a webhook.

  • n8n version: 1.104.1
  • **Running n8n via cloud
  • Operating system: windows 11
2

Hi, I have the same issues. At this point did you figured out how fix it. Can you help me ?

3

What events specifically from elevenlabs… Client(websocket for realtime like agent_response chunks) or Post-call(audio and transcript after call ends).

You can set as well a Initiation webhook to send dinamic variables and overriding the prompts etc…

Basically I have 3 webhooks(n8n and set as url in Initiation and Post call.), one triggers the call, 2nd is with dinamic variables when 11labs make a post request, and 3rd I listen for post call events.

But for real time is needed websocket (js or python) or how you want to fetch and display realtime data.

Working right now at a live call monitor, and digested 11labs Docs…

4

  1. Server → ElevenLabs (publish)

    • Anything that controls the agent or call must be sent over the WS, like:

      • user_audio_chunk (your microphone)

      • user_message (typed)

      • client_tool_call (like end_call or transfer_to_number)

      • contextual_update

      • pong

    These are published messages — no HTTP webhook triggers these in real time.

  2. ElevenLabs → Server (subscribe)

    • Events like:

      • conversation_initiation_metadata (contains conversation_id)

      • user_transcript

      • agent_response

      • audio

      • client_tool_call (if the agent calls a tool)

    • These are subscribed messages you receive over the WS.

  3. Webhooks (HTTP)

    • Only for post-call reporting or initiation.

    • They cannot deliver real-time agent events or trigger tools mid-call.

    • That’s why your initiation listener sees limited info, and post-call listener only sees the final transcription/audio/conversation_id.

5

Hi, I took a long break from things, but I’m trying to get back into things. It was awhile ago, and I’m not really sure if this worked or if it was a coincidence. In the security tab of my created ElevenLabs agent, under the Post-Call Webhook section, I selected the agent that I used (it’s odd because it’s calling back to itself…I think?) It’s been functioning since then. Hope this helps. By the way, there is now a video that you can watch linked right at the Post-Call Webhook section. I haven’t watched it yet, but I’m sure there will be some good information.

6

Glad that it solved your confusion.

Yes, it can be a bit tricky, but first you have to understand how platform sends/receive data.