Date/Time Formatter or HubSpot confusing date formats?

[jleonen.inctv]

Hey there,

Was there an update to the Date/Time Formatter? Or perhaps it's something HubSpot did to theirs? I was able to get special occasion reminders working and they were doing fine when all of a sudden earlier, I got a reminder for an event that happens on April 10 (04/10) when it's supposed to trigger reminders for October 10 (10/04).

I tried troubleshooting it in Pabbly Connect and found out that it is actually pulling in data from BOTH dates as you can see from the screenshots included. I hope things start running smoothly again. Thanks all for the amazing service and support!

 

[Supreme]

Was there an update to the Date/Time Formatter?

There are no recent changes or updates in the DateTime Formatter module.

Additionally, as evident in your workflow, you've utilized the Date Time Formatter with the MM/DD/YYYY format, whereas the date for the occasion is presented as DD/MM/YYYY, specifically 10/04 taken from your Hubspot.

Consequently, the DateTime formatting you've applied has interpreted it as MM/DD/YYYY (04/10).

 

[jleonen.inctv]

Hey @Supreme,

Thanks for getting back to me. If you check both screenshots of the HubSpot CRM response results, you will see that although I have the Date/Time Formatter set to MM/DD/YYYY, I did a test where I had 1 company have an anniversary date in MM/DD/YYYY format (04/10) and another in DD/MM/YYYY format (10/04) and it pulled both results from the HubSpot company search.

 

[Supreme]

Can you please share the Workflow URL in which you have tried the same?

 

[jleonen.inctv]

Hey @Supreme,

Here you go:

https://connect.pabbly.com/workflow...LDGxfS1ZSAFYAc1JLAi4EB1QuA04Ae1YDATJdA1B4VDU#

Thanks for the assist!

 

[Supreme]

The API response you receive originates from the Hubspot server, and Pabbly Connect does not intervene or alter the incoming API response in any way.

So, we recommend you check the date format filled for that company and contact the Hubspot support team for the same.

 

[jleonen.inctv]

Thanks @Supreme, it seems it's running ok again, but I will look into it more.