Calendar Caddie FAQ

Ghost is my target market, but you can actually embed it anywhere you can embed html & javascript. For example, check out Stumptown Savings' calendar. That's Beehiiv.

Small caveat: If you want to upload images for your calendar events, that requires Ghost (at least for now). You can put your images somewhere else and paste in links, or perhaps your feed items already have images (ideal).

Yes. Put the submissions embed on a separate page on your site, and configure Caddie (enable submissions and paste the link to that submissions page) to show the submit button.

Definitely. Nothing goes live until you approve it.

If you trust them, the fastest and most-automated way to get the events into Caddie would be for them to create a calendar (i.e. a free Google Calendar) and give you the address of its public feed. Then their events could appear on your site, no approvals or manual work needed!

Sure! You can either manually create your events, or create a public calendar using any tool you like (i.e. Google calendar) and add its feed to Caddie. I generally think maintaining a calendar outside of Caddie is slightly easier than making Caddie the source of truth, but you can do either, and for a small number of events, it really doesn't matter.

Sometimes what looks to a human like a perfectly good list of events is actually a hand-built page with no structure that automation can read. [Note to the owners of these types of pages: If my automation can't read it, neither can Google's web crawler, and you're missing out on traffic as a result.]

You can try the AI import tool (under "Custom" events) and paste in the contents of the page. It won't live update, but at least you'll get a static copy of their events.

Caddie's current automated event retrieval doesn't use AI to parse page contents (exception: applying categories and deduplicating events). It relies on the site having a machine-readable structure.

If AI whole page parsing is something you want, let's talk. It won't be a Caddie Lite/free offering, because it would require having an LLM check the page every night and assess whether any events listed had updates would be slow and token-intensive.

• Event deduplication uses AI to determine if two similar events are the same, handling the case where you have Caddie configured to pull events from feeds that have some overlap. (Before dispatching to AI, a simpler automation tries directly matching their names, locations, and times, but that is typically successful only if the two sources are pulling from a common source already.) If you don't want AI usage, I can disable this for your Caddie installation.
  
  The AI does not edit events, but it does judge which one should show up in the feed, if it detects duplicates.
• Event categories: A non-AI automation first attempts to assign categories based on your word matching and native category strings (if you configure them, and your source has them). So for example, if an event title includes "Trivia", you might set your trivia category up to automatically get applied, no AI needed. After this first categorization attempt, the automation sends uncategorized events to an LLM model to pick categories. If you don't want AI usage, I can disable this for your Caddie installation. If you'd like to reduce your AI usage, spend a little time setting up keywords.
  
  The AI does not create categories. It only chooses from what you've set up (or chooses not to categorize, if it doesn't find a good option.)
• "Import with AI" uses an LLM to parse your pasted in text and/or event flyer. In this case, the LLM does create the title, description, and date. Its prompt encourages it to use the exact language you've pasted in, but you should definitely review the output.