@dazed
It sounds like you're encountering an issue where the automation is triggering on every transcript message rather than waiting for the end of the call report. To ensure that the automation only triggers after the call has ended, you'll need to modify your VAPI event listener to check for a specific event that indicates the end of a call.
Here's what you can do:
1. Update your VAPI event listener to listen for a specific event that signifies the end of a call. This could be a 'call-ended' event or similar, depending on how your VAPI is configured.
2. Ensure that your automation in Make.com is set to trigger only when this specific event is received. You may need to use filters or conditions in Make.com to check for the correct event type.
3. If VAPI sends a specific message type or includes a particular flag in the message data when the call ends, use that to differentiate between partial transcripts and the final end of call report.
4. If you're not sure how to identify the end of a call event or if such an event is not being sent, you may need to implement a custom logic that waits for a period of inactivity or a specific signal from VAPI that indicates the call has truly ended.
If you're still having trouble, please provide more details about how your VAPI is configured to send end of call reports, and I can give you more specific advice. If this is a persistent issue that you cannot resolve with the available documentation and settings, it might be best to reach out to VAPI or Make.com support for further assistance.