I've been trying to get help for the VAPI + Make.com setup using Jannis video to setup outbound caller but its not working. Can anyone help as I am trying to setup an outbound caller and was trying to use Google Sheets or Airtable but I'm just having no success with this. I setup my API, my assistant ID, phone ID but when I try to run the make.com scenario nothing happens. ANy help or insight would be greatly appreciated.

@Steward C I'm sorry to hear you're having trouble setting up the outbound caller with VAPI and Make.com. Let's go through some troubleshooting steps to see if we can resolve the issue: 1. **API Configuration**: Double-check that your API key and other credentials are correctly entered in Make.com. A common issue is copying and pasting errors or extra spaces. 2. **Assistant ID and Phone ID**: Verify that the Assistant ID and Phone ID are correctly configured in your scenario. Ensure that these IDs match the ones provided by VAPI. 3. **Google Sheets or Airtable**: Make sure that your Google Sheets or Airtable base is properly connected to Make.com. Check if the correct sheet or table is selected and if the data is being read correctly. 4. **Make.com Scenario**: Review each module in your Make.com scenario to ensure that they are correctly configured and that the data flow between modules is logical and error-free. 5. **Logs and Errors**: Look at the execution history in Make.com for any errors or logs that can give you insight into what might be going wrong. 6. **Test Calls**: Try making a manual call using the VAPI to ensure that the service is operational and that there are no issues with your VAPI setup. If you've checked all these and are still facing issues, it might be helpful to provide more specific details about where the process is failing. Is there an error message? At what point does the scenario not behave as expected? Remember, you can always reach out to VAPI support for more detailed assistance with your setup. If you need me to perform any specific actions or checks, please let me know, and I'll be happy to assist further!

1. check 2. check 3. check In order to be able to run a make scenario (save it) you have to authenticate the module's you've added. 4. module are configured correctly. 5. logs don't report anything wrong. I am attaching screenshot showing what it says also. 6. Tested the call and agent works. I set up the agent using Jannis blueprint and put in all the info in that he said. The scenario goes through but I do not get a call. https://cdn.discordapp.com/attachments/1308895241876803644/1309331194386845777/image.png?ex=67413132&is=673fdfb2&hm=b73b8f3d422ab8213a892198f57183e66155c5d1cf185c2fc882f1b5e77c2c71&

@Steward C It's great to hear that you've thoroughly checked the configuration and that the logs show all processes were completed. Since the Make.com scenario runs through without errors and you've confirmed that the VAPI agent works with a test call, it seems like the issue might be with the connection between Make.com and VAPI or with triggering the actual call. Here are a few additional steps you might consider: 1. **Webhook Configuration**: If you're using a webhook to trigger the Make.com scenario, ensure that it's correctly set up and receiving data as expected. 2. **Action Module**: In your Make.com scenario, double-check the action module that is supposed to initiate the call. Ensure that it's correctly set up to use the VAPI to make the call. 3. **Data Mapping**: Verify that the data passed to the VAPI call action is correct, including phone numbers and any other parameters required to make the call. 4. **Scenario Activation**: Confirm that the scenario is active and not in draft mode. Sometimes scenarios need to be explicitly activated to run. 5. **Scheduling**: If your scenario is scheduled, ensure that the schedule is set correctly and that it's not set to run at a future time or date. 6. **Permissions**: Check if there are any permission issues that might prevent Make.com from making an outbound call through VAPI. If after these checks you're still unable to get the call to go through, it might be necessary to reach out to Make.com support for a deeper investigation into the scenario execution. They might be able to provide more detailed logs or insights into why the call isn't being placed even though the scenario completes successfully. If you have any specific error messages or additional details that you think might help diagnose the issue, please share them, and I'll do my best to assist you further.

@Steward C can you share your orgId, phone-number and assistant ids used with make.