Elyes | Low-Code Developer
05/28/2024, 1:57 PMVapi Support
05/28/2024, 1:57 PMVapi Support
05/28/2024, 1:57 PMjson
{
"transcriber": {
"provider": "deepgram",
"model": "nova-2",
"language": "cs",
"smartFormat": true
},
"model": {
"messages": [
{
"content": "Hello, {{customer_name}}. Your phone number is {{customer_phonenumber}}.",
"role": "assistant"
}
],
"provider": "openai",
"model": "gpt-4o"
},
"voice": {
"provider": "azure",
"voiceId": "andrew",
"speed": 1.25
},
"metadata": {
"customer_name": "John Doe",
"customer_phonenumber": "+1234567890"
}
}
This JSON payload uses placeholders (e.g., {{customer_name}}) within the message content that can dynamically insert data provided in the metadata object. When crafting your HTTP request from Make.com, ensure that you replace these placeholders with the actual dynamic data fields you retrieve from your workflow.
For sending an SMS with Twilio integrated into this process, you would typically handle this on your backend server after receiving a webhook from Vapi, or directly through Twilio’s API using the information extracted or passed through from the assistant session.
Remember to replace placeholder fields and values with actual data and ensure your API keys and tokens are securely handled.Elyes | Low-Code Developer
05/28/2024, 1:59 PMSahil
05/28/2024, 2:57 PMSahil
05/28/2024, 2:57 PMElyes | Low-Code Developer
05/28/2024, 3:27 PMElyes | Low-Code Developer
05/28/2024, 3:29 PMSahil
05/28/2024, 3:41 PM