Why Google Calendar + dassi
Google Calendar is already where the work happens. dassi adds the missing layer: it can read what’s on the page and then take actions (draft, classify, fill, log, summarize) without you rebuilding context in a chat box.
What to automate in Google Calendar
- Email → event creation: Extract meeting details from email threads and create pre-filled events.
- Meeting prep briefs: Compile attendee context from email/CRM/LinkedIn into a single brief.
- Conflict-aware travel booking: Mark busy/free conflicts on booking calendars without official integrations.
Quick start
- Open Google Calendar in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “Turn this into a calendar invite for Thursday 3pm at Blue Bottle.” (from “Add to Calendar” Button Inside Any Email)
- “Add a 25-minute buffer and include the Zoom link if present.” (from “Add to Calendar” Button Inside Any Email)
- “Build a prep brief for this meeting: attendee backgrounds + recent threads.” (from Meeting Prep Panel Injected Into Calendar Events)
- “Pull last touchpoints from Salesforce and summarize them.” (from Meeting Prep Panel Injected Into Calendar Events)
- “Check my calendar and mark conflicts on this date picker.” (from Travel Booking Page That Shows Your Calendar Conflicts)
- “Only show options that avoid conflicts on weekdays.” (from Travel Booking Page That Shows Your Calendar Conflicts)
- “Summarize what’s on screen and propose next actions.”
- “Do the safe part first (draft / label / preview), then ask me before any irreversible action.”
- “Turn this page into a clean checklist I can follow.”
Safety checklist
- Tell dassi: “Never submit/send without confirmation.”
- If the page contains sensitive data, ask for redaction or aggregated outputs (totals-only, no PII).
- Prefer reversible actions first (drafting, labeling, notes) before destructive ones.