Short answer: our docs don’t recommend using raw fetch calls inside n8n Cloud. For n8n, the supported paths are:
Use the native ElevenLabs node in n8n Cloud (no HTTP nodes or custom code required). (elevenlabs.io)
Or call your n8n workflow from an ElevenLabs Agent via a Webhook tool (i.e., integrate through webhooks rather than inline fetch code). (help.elevenlabs.io)
Why your “fetch” snippet from “25daysofagents” likely fails:
That code is intended for a general JS environment, not the n8n editor. Our official guidance for n8n Cloud is to install and use the ElevenLabs node directly, or integrate via webhooks from an Agent—so custom fetch code isn’t part of the documented n8n setup. (elevenlabs.io)
What to do:
In n8n Cloud, add the ElevenLabs node from the Nodes panel and build your workflow there. (elevenlabs.io)
If you’re triggering n8n from an Agent, add a Webhook tool in the Agent and point it at your n8n webhook URL. (help.elevenlabs.io)
Note: I couldn’t find any “25daysofagents” article in our official help center or blog to verify that specific snippet. If you share the exact link, I can check it. Otherwise, for issues, please contact support. (help.elevenlabs.io)
random hatch
near valve