Check event times before importing a calendar file
Review event times and zones, save the iCalendar draft as .ics, then manually inspect an import in a test calendar.
Execution environment and usage
AI / software
Text preview; plain-text .ics file; Google Calendar desktop test import
Where to operate
Chat produces a readable preview and copyable iCalendar text; manually save an .ics file and test it at https://calendar.google.com.
Getting started
- Supply complete event names, start/end times, zones and recurrence; review the preview without adding unspecified attendees or reminders.
- Request iCalendar text after review. Use supported file output if available, or paste it into a plain-text editor that can save .ics; ensure the file is not named .ics.txt.
- On a computer open https://calendar.google.com → Settings → Import & Export and choose the .ics file.
- Explicitly select your prepared test calendar before Import; check dates, zones and recurrence rather than accepting the default primary calendar.
Setup and plan requirements
A copyable-text assistant, plain-text editor able to save .ics, desktop Google Calendar account and prepared test calendar. Exclude unauthorized recipients.
Prompt portability limits
The preview and iCalendar text are portable. The user saves and imports the file; chatbot calendar-write access is unnecessary.
Usage limitations
Google documents editing .ics in a text editor and desktop import. Format and time zones still need testing; import is not ongoing sync. This review generated or imported no file.
Environment sources
適用情境 / When to use
Review event times and zones, save the iCalendar draft as .ics, then manually inspect an import in a test calendar. Chat produces a readable preview and copyable iCalendar text; manually save an .ics file and test it at https://calendar.google.com. AI prepares the draft; a person completes the setup, export or validation steps below. Original case: A Reddit commenter describes having the bot generate .ics invitations that they accept themselves.
步驟 / Steps
- Supply nonsensitive event names, dates, start and end times, time zones and locations; resolve missing details first.
- Inspect a readable preview, including all-day, overnight, recurrence and reminder semantics. Do not add unspecified settings.
- If file output is supported, create a draft .ics for your inspection. Check it in a test calendar before importing selected events yourself.
提示詞 / Prompt
From [sanitized event details], preview names, dates, start and end times, time zones, locations and recurrence rules. Ask about ambiguous dates or missing times rather than guessing. Once details are complete, you may produce a draft .ics for my inspection. Do not add attendees, send invitations, sign in or write to any calendar.
留意事項 / Cautions
- Generating or emailing an invite does not prove calendar insertion. Repeated imports can create duplicates.
- Do not provide Apple passwords, create bot accounts or expand sharing permissions. Keep recipient addresses and sensitive events out of test files.
來源限制 / Evidence limits
The evidence is one user comment, not a demonstrated two-way synchronization system. No file or import log is supplied, and the date is unconfirmed.
流程說明 / Workflow note
The following is an original, untested exercise, not a reproduction of the reported session. Check available features and permissions, then adapt it to your own constraints.
原始工具組合 / Original tool stack
Grok Bot; generated .ics invites; email; manual calendar acceptance
Source checked: 2026-10-19