Hello, I am creating a receptionist for restaurants. Currently used tools: Custom webhook (from Make.com, and with ) Airtable (Associated modules added to Make.com workflow) In the prompt, I have the AI seek both date and time in the needed formats with both: "When scheduling a reservation, collect the reservation date and time from the caller. MAKE SURE YOU USE THESE FORMATS FOR DATE AND TIME!: Date format: YYYY-MM-DD (e.g., 2025-12-16) Time format: 12-hour with AM/PM (e.g., 2:00 PM)" After running the workflow, Vapi sends the date/time data (at least it is assumed so), yet the parameters are returned as "invalid". The two properties are named "requested_start" for start date/time, and "requested_end" for end date/time in the 'request body' category in the tool I set up in Vapi. ONE OF THESE TWO ISSUES MAY BE OCCURING Nothing about the "requested_start" property is sending anything related to date or time to the webhook in the first place (I would need help knowing how to define that in the schema). The incorrect date/time format is being sent, despite specific instructions in the prompt for the only acceptable formats (I would need help knowing how to force the formatting outside of the prompt alone). Here are some screenshots: requested start and requested end are not parsed each time the scenario runs (Make.com Screenshot): https://cdn.discordapp.com/attachments/1428213272095756336/1452716776227078238/3ffb514f8112444b188182cc0f530ac9.png?ex=694ad36d&is=694981ed&hm=665d545c30dc942f69389de168d4ae5e4f2bdfdd66f451dcfbbb7ae63032903d validation for parameters failed + automatic rollback response (Make.com Screenshot): https://cdn.discordapp.com/attachments/1428213272095756336/1452716839556743241/eacb9cb631715a510384077b85a14b90.png?ex=694ad37c&is=694981fc&hm=ec97784229c3502a219ac48a05d3366ebd2dbce425568ee9b930b84bb82ce971 All help is appreciated, and additional information can be provided upon request. Thank you.

Thanks for sharing the details and screenshots. It looks like the main pain point is ensuring requested_start and requested_end are correctly parsed and formatted before reaching Airtable, which is where the “invalid” errors come from. I can help set up a reliable workflow to enforce proper date/time formatting and handle missing or misparsed values. Could you share the exact sample output your AI is sending for these fields so I can suggest the precise mapping and parse functions @Babayaga

Hi, I am sorry for the delayed response. The issues you described might be related to the prompt. To better understand the issue, Could you provide some Call IDs where you were facing this issue? This will help me review the system prompt, and the webhook calls as well.