Hi I'm using Vapi and n8n. I've noticed that the end of call Webhook gets triggered 2 times. Any suggestions?

Hi there! 👋 I understand you're experiencing an issue where the end-of-call webhook is being triggered twice when using Vapi with n8n. This can definitely be frustrating, but I can help troubleshoot this! Here are some potential reasons and solutions for this issue: ### Webhook Configuration Issues - Check your webhook URL settings in the Vapi dashboard to ensure there's no misconfiguration. Double-check that the URL is correctly set up without any typos or omissions. [According to our documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334280135683084328), there might be multiple places to configure webhook URLs (event-specific, application-level, account-level). - Verify the

endCallFunctionEnabled

setting is properly configured in the Vapi dashboard. [Some users have found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) that setting this to true helps resolve similar issues. ### n8n Workflow Configuration - Implement redundancy checks in your n8n workflow to identify and handle duplicate webhook calls. You could add a unique identifier check to prevent processing the same end-of-call event multiple times. - Review your event handling logic to ensure it's correctly interpreting the events sent by Vapi. [Our documentation suggests](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1316958070177403011) that incorrect event handling can lead to multiple triggers. ### Network and Server Issues - Check for connectivity problems between Vapi and n8n. Network issues could cause retries, leading to multiple triggers. - Review server logs in both Vapi and n8n for any errors or messages that could indicate what's going wrong. [This can help identify](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362) if there are failed attempts and what the reasons might be.

Thank you for reaching out to us. We've received your message and will get back to you as soon as possible.