id,user,created_at,full_text,retweeted_status,quoted_status,place,source,truncated,display_text_range,in_reply_to_status_id,in_reply_to_user_id,in_reply_to_screen_name,geo,coordinates,contributors,is_quote_status,retweet_count,favorite_count,favorited,retweeted,possibly_sensitive,lang,scopes
1453187165291118597,33521530,2021-10-27T02:29:53+00:00,@stubailo @stolinski y u roasting my design doc https://twitter.com/swyx/status/1453187165291118597/photo/1,,,,1f89d6a41b1505a3071169f8d0d028ba9ad6f952,0,"[21, 47]",1453186117289734146,12767662,stubailo,,,,0,0,2,0,0,0,en,
1453400900697874433,33521530,2021-10-27T16:39:12+00:00,"@stubailo @stolinski responding quickly can be done with a short workflow or signalling into and querying out of a long workflow.
both are fine, so long as it isn't realtime. 

i have a nextjs sample here that shows how you can embed a temporal client in a serverless endpoint 
https://github.com/temporalio/samples-typescript/tree/main/nextjs-ecommerce-oneclick",,,,1f89d6a41b1505a3071169f8d0d028ba9ad6f952,0,"[21, 301]",1453394921470132224,12767662,stubailo,,,,0,0,0,0,0,0,en,