Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Salesforce lead setup - 'cannot deserialize instance of time' error

  • September 17, 2021
  • 3 replies
  • 1197 views
T
Forum|alt.badge.img

I have created a Zap to setup a lead on Salesforce. I pass the time value in the “03:00:00 PM” format to the time field of the Salesforce lead. But Zapier takes it in the “2021-09-17T15:00:00-05:00” format. Why?

And then, it throws the following error.
Could not create record of the "Lead" object: Cannot deserialize instance of time from VALUE_STRING value 2021-09-17T15:00:00-05:00 or request may be missing a required field at [line:1, column:287]

Attaching screenshots.

Time value that I pass.

 

Time value that Zapier takes and throws an error.

 

Looking for help. Thank you in advance!

Best answer by christina.d

Just wanted to pop in here as saw we have an existing bug report open for this very same error, where a datetime rather than a time value is passed to Salesforce.

I’ve added @thinker500 to the list of affected users. While we don’t have an ETA on when it will be resolved we’ll be sure to email as soon as it has been. :)

Hey there, squad! I wanted to swing by and let ya’ll know a fix for this is now live and the bug officially closed. 🎉

Thanks for for your patience on this! 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • September 17, 2021

Hi @thinker500 

Salesforce help article about expected datetime formats: https://help.salesforce.com/s/articleView?id=000325035&type=1

Try using a Formatter > Date / Time > Format step: https://zapier.com/help/create/format/modify-date-and-time-formats-in-zaps

 

Additional info about the Date/Time field format in Zaps: https://zapier.com/help/create/basics/different-field-types-in-zaps#step-1

⚡ Troy Tessalone - AutomationAce.com | Platinum Zapier Solution Partner | #1 Zapier Community Contributor
SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • November 17, 2021

Just wanted to pop in here as saw we have an existing bug report open for this very same error, where a datetime rather than a time value is passed to Salesforce.

I’ve added @thinker500 to the list of affected users. While we don’t have an ETA on when it will be resolved we’ll be sure to email as soon as it has been. :)

christina.d
Forum|alt.badge.img+9
  • christina.dZapier Staff
  • Zapier Staff
  • Answer
  • November 15, 2022

Just wanted to pop in here as saw we have an existing bug report open for this very same error, where a datetime rather than a time value is passed to Salesforce.

I’ve added @thinker500 to the list of affected users. While we don’t have an ETA on when it will be resolved we’ll be sure to email as soon as it has been. :)

Hey there, squad! I wanted to swing by and let ya’ll know a fix for this is now live and the bug officially closed. 🎉

Thanks for for your patience on this! 

Terms & ConditionsAccessibility statement