Having trouble with the timestamp coming from VAPI to Airtable via Make. For example, a call made on 11/12/2024 at 12:16pm shows up as 11/22/5683 12:43pm,

@LongBeard It sounds like there may be an issue with the date format conversion between VAPI and Airtable when using Make (formerly Integromat). To resolve this, you'll want to ensure that the timestamp from VAPI is being correctly formatted and parsed in Make before it is sent to Airtable. Here are a few steps you can take to troubleshoot and fix the issue: 1. **Check the VAPI Timestamp Format**: Verify the format of the timestamp that VAPI is providing. It should be in a standard format like ISO 8601. 2. **Inspect the Make Scenario**: Look at the Make scenario that's handling the data transfer. There might be a module that formats the date, and you'll want to ensure it's set up correctly. 3. **Adjust Date Formatting**: If necessary, adjust the date formatting in Make to match Airtable's expected format. You can use Make's built-in date and time functions to transform the timestamp. 4. **Test the Scenario**: Run a test with a known timestamp to ensure that the formatting is now correct. 5. **Check Time Zone Settings**: Ensure that the time zone settings in both VAPI and Airtable are consistent, as a mismatch could cause unexpected date and time conversions. If you need further assistance with the specific settings in Make or with VAPI's timestamp format, please let me know, and I can provide more detailed guidance. If the issue persists, you may need to reach out to Make's support for more specialized help with their platform.

@Vapi The timestamp data just comes directly from VAPI to Make's webhook and then sends it to Airtable. This is how I've always had it done, it only recently changed, even though I haven't touched it

@LongBeard It seems like there might have been an update or change in the way timestamps are handled by either VAPI, Make, or Airtable that is affecting your workflow. Here's what you can do to troubleshoot the issue: 1. **Verify Timestamps in VAPI**: Check the format of the timestamps directly from VAPI to ensure they are still being sent in the correct ISO 8601 format. 2. **Inspect Make's Webhook Data**: Look at the data received by Make's webhook to confirm that the timestamp is correct when it arrives from VAPI. 3. **Check for Updates in Make**: Review any recent updates or changes in Make that might have affected how data is processed or formatted. 4. **Examine Airtable's Field Settings**: Ensure that the field in Airtable where the timestamp is being stored is still configured to accept the date-time format without any changes. 5. **Test with a Manual Entry**: Try manually sending a correctly formatted timestamp from Make to Airtable to see if it is processed correctly. 6. **Contact Support**: If the issue is not resolved by the above steps, consider reaching out to Make's support team for assistance, as they may have insights into recent changes that could be affecting your workflow. If you need assistance with checking the timestamp format in VAPI or any other specific actions, please let me know, and I can guide you through the process.

@Vapi No time stamps are not being sent from VAPI is not correct, here is an example +056836-11-22T17:43:45.000Z

@LongBeard The timestamp you've provided (

+056836-11-22T17:43:45.000Z

) appears to be incorrect as it suggests a year far in the future (

56836

). This is likely a formatting issue or a bug in the system generating the timestamps. Here's what you can do to address this: 1. **Check VAPI Configuration**: Ensure that the configuration for timestamp generation within VAPI is correct. There might be a setting that has been altered which is causing the incorrect timestamps. 2. **Contact VAPI Support**: Since the timestamp format is not standard and is coming directly from VAPI, it would be best to reach out to VAPI support for assistance. They can provide more insight into why the timestamp is being generated incorrectly. 3. **Workaround in Make**: If you need an immediate fix and the timestamp from VAPI includes the correct time (ignoring the incorrect year), you could use Make's date and time functions to replace the year with the current year before sending it to Airtable. 4. **Monitor for System Updates**: If this issue started happening without any changes on your end, it's possible that an update or a bug has been introduced in VAPI. Keep an eye on any announcements from VAPI regarding updates or fixes. If you need further assistance with contacting VAPI support or implementing a workaround in Make, please let me know, and I can guide you through the process.

@Vapi "Check VAPI Configuration: Ensure that the configuration for timestamp generation within VAPI is correct. There might be a setting that has been altered which is causing the incorrect timestamps." Regarding the above, how do I do that?

@LongBeard To check the VAPI configuration for timestamp generation, you would typically need to access the settings or configuration panel within the VAPI platform. However, as an API, VAPI may not provide direct user interface options for configuration. Here's a general approach you can take: 1. **Review Documentation**: Check VAPI's official documentation for any information on timestamp configuration or related settings. 2. **API Settings**: If VAPI provides an API endpoint for configuration settings, you can use that to retrieve and verify the current timestamp settings. 3. **Check Integration Code**: If you have access to the code that integrates VAPI with your system, review it to ensure that the timestamp is being handled correctly. 4. **Contact Support**: If you're unable to find the settings or if the documentation does not provide clear guidance, the best course of action would be to contact VAPI support directly. They can provide specific instructions or look into the issue on their end. If you need assistance with contacting support or have other questions about VAPI, please let me know, and I can help guide you through the process.

hey @LongBeard can you share the call id?

@Shubham Bajaj a1d17d59-e2b9-4dd6-8567-f3c50e3c19db

Hey you might, have mixed different call date time properties, below I am listing all four and do let me know which of these your using.

json
    "started_at": "2024-11-12 17:16:21.067+00",
    "ended_at": "2024-11-12 17:19:10.427+00",
    "created_at": "2024-11-12 17:16:19.925+00",
    "updated_at": "2024-11-12 17:19:17.823+00",

This is the setup that has been working until recently. The end of call report is sent from VAPI to Make webhook, and then an Airtable module in Make with "message: timestamp" with the timestamp data is sent to Airtable. Please see the image. Since nothing has changed on my end this would have to something that changed with VAPI. https://cdn.discordapp.com/attachments/1305982257969762434/1307038332957757491/image.png?ex=6738d9ce&is=6737884e&hm=dfbd13be66d1537f62fcc6ca6b0a3b19c30f5943d59faf5c4e89cd1a1ea2f729&

timestamp is not the actually value you should be using instead your supposed to use either of these started_at/ended_at/created_at.

@Shubham Bajaj ok I will change it and see the difference. But like I said, I have been using timestamp all this time with no problems.

Do update me once your done with it.

I updated it as you can see in the screenshot. The call returned no values. https://cdn.discordapp.com/attachments/1305982257969762434/1307387531855401123/image.png?ex=673a1f05&is=6738cd85&hm=dea94b874428cbe5516d1af2f38d9a670c029abed743ef923cbbf8cf4ac90ccd&

@LongBeard its startedAt and endedAt, can you redetermine your structure. If possible join discord OH today for live tech support. https://cdn.discordapp.com/attachments/1305982257969762434/1308107741587312660/Screenshot_2024-11-18_at_10.01.56_PM.png?ex=673cbdc5&is=673b6c45&hm=e37807dbda3f252cbbc911f110a925ef958a6cda580df68358b91b3d964ccc13&