I am building a zap to trigger a new row in MySQL when I create a new record in Adalo. My issue is that Adalo stores their date in the format YYYY-MM-DDT00:00:00:000Z and MySQL store it as YYYY-MM-DD.
![](https://uploads-us-west-2.insided.com/zapier-ca/attachment/935ee0c8-c3b9-4f61-8a93-e1ecbc46ec32.png)
![](https://uploads-us-west-2.insided.com/zapier-ca/attachment/68c4ed6a-ec4d-4355-bc58-a931fbd810ba.png)
As a result, I’ve created a zap action to change the format of the date input to one that works with MySQL.
![](https://uploads-us-west-2.insided.com/zapier-ca/attachment/d3a96114-8145-4ca5-ad95-5db138c9d94b.png)
The following two screenshots show this process in action with the date input, and the finished test with final date output.
![](https://uploads-us-west-2.insided.com/zapier-ca/attachment/26466ec6-32c7-4024-9e9e-9bfec0806a00.png)
![](https://uploads-us-west-2.insided.com/zapier-ca/attachment/1a4c89f6-384d-4314-8fc7-278f2d685823.png)
I have set up the final step to populate the Date Created column in MySQL with the date output from the reformatting step (now it’s in the form YYYY-MM-DD)
![](https://uploads-us-west-2.insided.com/zapier-ca/attachment/9cbe36a0-a1f5-4e8f-9730-516380584eb0.png)
However, when I run the final step I still receive the same error that the date created in MySQL cannot be of the format YYYY-MM-DDT00:00:00-05:00. The new row sent to MySQL shows a Date Created with the format YYYY-MM-DD. Any advice on how to address this issue and have the date formatting allow for a successful zap build is greatly appreciated.
![](https://uploads-us-west-2.insided.com/zapier-ca/attachment/8d85c2b8-973b-4694-9713-00a17e755aca.png)
Best answer by Troy Tessalone
View original