After reviewing the Twilio and ElevenLabs documentation, it appears there's a method to initiate outbound calls using Twilio while incorporating a voice from ElevenLabs.
There are two requirements that I'm unsure about regarding their feasibility or necessity within a self-hosted callin.io instance, or if they necessitate hosting on a separate container:
- Node.js 16+
- ngrok for local development.
I have a Google Sheets document containing the records I need to call. My goal is for the workflow to dial the numbers sequentially, and upon call completion, trigger a webhook to route the call's returned information to a different sheet.
Has anyone successfully implemented Twilio outbound calls with ElevenLabs voice yet?
Hello, I'm facing a comparable situation and am quite keen to learn if this is achievable.
Could you please share how this can be done?
My main hurdle is the requirement for Node.js 16+ and obtaining the necessary files from the conversational-ai-twilo clone on GitHub. Regarding ngrok, I haven't yet managed to get Traefik and Docker working with SSL, but I can see how ngrok is easily integrated into the Docker stack, whether using my own domain or their free option.
I've located the ElevenLabs nodes, and they do offer the following features. However, a complete conversational agent with voice functionality isn't included.
- Text to speech: Convert any text into high-quality, lifelike, context-aware speech audio files that you can manage within your workflow.
- Speech to speech: Transform your voice into another character's, retaining emotions and delivering with consistency.
- Generate voice: Create a new voice based on parameters like age, gender, and accent. Add it to your library and begin using it in your workflow.
- Clone your voice: Duplicate your own voice from an audio file and utilize it in your workflow for text-to-speech or speech-to-speech applications.
I did notice how
I'm quite surprised that it seems no one has implemented this yet…
I concur. Quite unexpected!
I've given it a shot and will share my progress to see if it can help us all move forward.
As well, I am at this point in my roadmap:
https://cgrist.great-site.net
My understanding is that callin.io manages all of this internally, for both inbound and outbound calls. It also integrates quite smoothly with Twilio. However, you do pay for this convenience.
Doesn't the primary reason for using Twilio/ElevenLabs directly for outbound calls involve reducing expenses? If so, integrating callin.io seems to counteract that objective.
I will look into this callin.io API, thanks!