Live data from Hacker News

Building an email-to-calendar LLM

ngacho.com

1–10 of 46 posts

Re: Building an email-to-calendar LLM

#4
I used to use calendar integrations for these kind of things. Then I realized I'd prefer to have the low priority stuff disappear until I have to deal with, so I switched to followupthen.com and have been happy with it. A nice effect is that it creates a paper trail so I know how many times I've put things off.

Re: Building an email-to-calendar LLM

#8

I'm looking at the AppScript site. Is this like PowerAutomate, but for G Suite products? Also I don't know why, looking at the site makes me think it's a candidate that Google is going to kill off without warning: https://www.google.com/script/start/

It stands out that it doesn't follow the Design System of many other Google products - wonder if that means it has its own fiefdom.

Re: Building an email-to-calendar LLM

#9

I'm looking at the AppScript site. Is this like PowerAutomate, but for G Suite products? Also I don't know why, looking at the site makes me think it's a candidate that Google is going to kill off without warning: https://www.google.com/script/start/

Apps Script is positively ancient at this point, first released in 2009: https://en.wikipedia.org/wiki/Google_Apps_Script

It's one of the Google products I worry least about, mainly because there are 15+ years of existing Google Sheets documents that people have built using it at this point. I don't think even Google would lightly break THAT many of their existing (often paid) users.

Re: Building an email-to-calendar LLM

#10

Just use CALDAV; it's designed for making calendar entries automatically via email. I'm not hip with the fashion for putting an LLM into everything. I think it's lazy.

If I'm generating the data, sure, I'll use CALDAV.

But for ingesting unstructured data I didn't generate, I'm going to reach for an LLM now (provided latency isn't an issue).

Post reply on HN