#Hello everyone,I'm looking for help from anyone who has already used ElevenLabs.I'm currently t

1 messages · Page 1 of 1 (latest)

cursive leafBOT
#
AI-generated Answer for vestielpichichi

Short answer: You can wire ElevenLabs to n8n in three supported ways, depending on when you want the workflow to run.

Option A — Trigger n8n during the live call (recommended for “do X now” actions)

  • In n8n: Create a Workflow with a Webhook trigger (POST) and copy the production URL.
  • In ElevenLabs: Add a Webhook Tool to your agent and paste the n8n Webhook URL. Include any auth headers your n8n endpoint expects. The agent can then call this tool mid‑conversation and pass parameters; your n8n flow returns a JSON result the agent can speak/use.

Option B — Receive full call data after the call (post‑call webhooks)

  • Purpose: Collect the transcript/analysis (or full audio) after analysis completes and hand it to n8n.
  • In ElevenLabs Settings: Create a Webhook and subscribe to one or both event types:
    • post_call_transcription (full transcript + analysis + metadata)
    • post_call_audio (minimal payload + base64 audio)
  • Point that webhook to your n8n Webhook node. Your handler must:
    • Return HTTP 200 quickly (failed deliveries are auto‑disabled after repeated failures).
    • Verify the HMAC signature in the ElevenLabs-Signature header (format t=timestamp,v0=hash; hash = HMAC-SHA256 over “timestamp.request_body”).
  • Note: As of August 15, 2025, post_call_transcription includes has_audio, has_user_audio, and has_response_audio fields; ensure your n8n JSON parsing tolerates these.

Option C — Inject context at call start (for inbound Twilio numbers)

  • ElevenLabs can call your webhook at call initiation with caller_id, agent_id, called_number, call_sid. Your endpoint (n8n Webhook) returns conversation-init variables/overrides used to start the call.

Practical n8n setup tips (from the docs above)

  • Use a Webhook node (POST). If you’re powering a live tool call (Option A), have your last node return the JSON your agent expects; for post‑call (Option B), just ACK with 200 after signature validation, then process asynchronously.

FYI: ElevenLabs is also a verified integration on n8n Cloud (use the native nodes when building from n8n toward ElevenLabs).

If you share which of the three flows you want (during call vs. after call vs. call start) and what’s failing (no delivery, signature errors, or agent not invoking the tool), I can map the exact doc-backed steps to fix it.

radiant current
#

about the option A in n8n how should I configure the when and how to respond to the webhook $