About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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

DynamoDB integration with Google Sheets

  • 30 December 2022
  • 2 replies
  • 74 views
A
Userlevel 1

Hi! I'm trying to connect the integration of data from a DynamoDB table to a Google Sheets table.

But at the stage of connecting DynamoDB, the timestamp field is invisible, although there is such a field in the table and it has the unix timestamp format. Instead of the timestamp field, the “id” field is defined, but the integration does not work with it.

Can someone tell me what could be the reason?

icon

Best answer by Danvers 30 December 2022, 14:46

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

2 replies

Danvers
Userlevel 7
Badge +12

Hi @Andrii Datskiv, welcome to the Community!

 

We’ve found that some users have trouble with their timestamp field when it’s set in Unix format because it’s incorrectly read as a text field.

We know that at least one user has been able to reference their  Number-type timestamp field by declaring it as a Custom Value: 

 

 

​I hope that helps, please let us know if you have any questions!

A
Userlevel 1

Thanks! That way is working!

Terms & Conditions