thank you all

Hey 👋 when you call the ElevenLabs API in n8n, the JSON output depends on the specific endpoint you’re hitting. For example: - Text-to-speech (TTS) usually returns an audio stream (base64 or binary) rather than plain JSON. If you set Response Format to JSON in n8n, you’ll mostly see metadata like content-type, size, etc., and the actual audio data in the body. - Voices / Models endpoints will give you standard JSON objects (voice IDs, names, labels, etc.). If you share which endpoint you’re trying to use, I can help map out the exact JSON structure you’ll get inside n8n

Hey 👋 I’ve run into this before — you’re right, n8n generates its own webhook URL and you can’t just swap it for something else. The way around it is to use the webhook n8n gives you, then connect your Tally form to that link. If you want to keep your own URL for consistency (instead of the n8n one), you can put a reverse proxy or use a service like Cloudflare Workers/NGINX to forward requests from your custom link to the n8n webhook. That way Tally still points to your link, but everything ends up in n8n seamlessly. Happy to walk you through the setup if you’d like

congratulations

congratulations