Would be helpful for managing events for us.

Thank you for your suggestion! Currently, the Google Calendar Tool in Vapi supports standard event fields but does not natively allow adding custom metadata fields to events. To better understand your needs, could you share an example of the type of custom metadata you would like to include with your calendar events? Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)

Whether you would like to request certain metadata fields or all of them, please submit your feature request to our request board.

Done, thank you. Its less of an explicit metadata field request, we want to track booked meetings later for post processing (cancelation, rescheduling, etc) so we need a unique identifier for the meeitng. Either Google's EventID or our own preset customID that we can pass to VAPI to incldue in the event metadata https://cdn.discordapp.com/attachments/1380117110167965706/1380449991998439464/image.png?ex=6843ebbd&is=68429a3d&hm=05b33aa672b8619a09695ba5d2d313642f1c7fab98aa6414befb24bc2f6fcdd5&

Thank you for the submission and the info. It helps with understanding the use case

Just realizing that for #1, can use custom metadata that we pass into VAPI from the trigger side as vars in a tool call?

Depending on what metadata specifically you would like to send, just make sure to follow the correct format from the API:

Been doing a bit more digging, finding that the Calendar Booking tool for google you guys already have returns the EventID but passing that along to the Structured Data is problematic because I think your VAPI agent is not connected to the structured data output. I'm assuming the structured data output is coming from transcription only and does not have access to the messages for tool responses and so cannot output the data correctly. This has been the case for other structured data, e.g. a date for the booked meeting when spoken by the VAPI agent gets passed correctly, but if it was cut-off by the caller for example, it won't go through to the structured data.

Yes it does include tool-call messages, so you could possibly use that as a workaround