Hello, we are using webhooks to send sign up data to an external API. The site is set to run Central Standard Time/Chicago, USA, time. We’ve noticed that when an entry comes in, the “Entry Date” merge tag in the webhook sends the time stamp on the entry some 5 hours later than when it came in.
Attached are screenshots of the entry, showing the entry date, the webhook showing the “Entry Date” merge tage being used, and the webhook logs showing this entry with the incorrect “Entry Date” being sent.
This is posing a big problem for us, as this sign up date is a critical piece of what we are collecting. Any idea why the “entry date” being sent in the webhook is different from the entry date saved with the entry?
Gravity Forms stores the entry date in the database in UTC, when it gets displayed in the entry detail the stored UTC date gets converted using your site’s timezone setting.
If you use the {date_created} merge tag instead of selecting the entry date option the output of that merge tag will be converted to your site’s timezone setting.
Using the format modifier on it like the example below would also output the entry date in the same format as the entry date option, but the entry date will be converted to your site’s timezone.
Hello Karl, thanks for your response. I’m a bit confused, we are using the “Entry Date” merge tag in the webhook, and the entry date is showing correctly when viewing a single entry. So why would this entry date then get changed when it’s used in a webhook rather than send the exact same entry date associated with the entry?
In your screenshot, the MemberCardLastUpdated mapping is not using the merge tag, it is using Entry Date choice in the drop down, which sends the raw entry value (UTC) for the date_created property. To send the value adjusted to the site timezone or formatted, you need to select the add custom value choice in the drop down and then enter the merge tag Karl suggested.
Thanks Richard, that cleared this up for me. I confusingly referred to the “entry date” as a merge tag as it was an automatic option listed in the webhook dropdown despite us not having a field for “entry date.”
It looks like the entry date shown in the admin for each entry has already taken the saved UTC formatted date and converted it based on our timezone settings, rather than that date being what is actually shown in the database.
This did the trick, now the webhook is showing the time sent as almost identical as what our entry date is showing.
