Any fans of Fantastical’s natural language entry for calendar events will like this one. Basically, I have recreated the same functionality in Drafts using JavaScript. Events can be added on multiple lines and then instantly added to the calendar, no pinging back and forth with URL schemes.
Works beautifully. This post was picked up on my Apple News newsfeed and I installed it straight from there. I think I will be ditching fantasical too.
DThat worked pretty well. I have some calendars that are two words, first word is identical but doesn’t seem to be picking the second word up for the / technique. Any suggestions for that?
Also, as a note I put “Lunch on Monday” and it added it to the previous Monday instead of the next Monday. I feel it should assume the next occurring Monday vs the past one unless I’m overlooking some other sort of use-case for why it works that way.
This creates events using iOS/macOS APIs, which can write to any calendars you have configured on your device. If you have your Google Calendars setup in iOS Settings, it can work with them.
For some reason, this is not respecting my default calendar. It is sending everything to Family which I do not even use. My default Calendar is simply called “Calendar” and if I add the /c at the end of the line, it works fine. I just don’t want to add that for every line. Any ideas?
Hello all, just to let you know I’ve pushed a small update to this script which fixes an issue where dates were not being reliably assumed to be in the future.
You are right that the forward slash syntax does not currently support spaces. However, it may not be the best thing for me to enable that as it could cause other issues, for example the /calendar would always have to be at the end otherwise anything that comes after would be interpreted as part of the name of the calendar.
The issue with events being created in the past should now have been fixed. Please re-install from the Action Directory.
I love the script and rely on it for adding stuff to my iPhone calendar. Unfortunately, it seems to be broken after the recent app (or iOS) update. I get the following error message: