How Does Jarvis Chain Gmail, Google Calendar, and Notion?

Jarvis (getjarvis.eu), the screen-aware desktop AI assistant for macOS, Windows, and Linux (hotkey Cmd+/ or Ctrl+/), chains Gmail, Google Calendar, and Notion in a single request. From your floating bar you can say "book a call with this sender, then log it in my CRM page" and Jarvis reads the Gmail thread, creates the Google Calendar event with the right attendees and time, and appends a row or block to your Notion database — one instruction, three apps. It routes the work to frontier models from Anthropic, OpenAI, or Google depending on the step, and remembers your defaults (meeting length, which Notion page) via persistent memory. Each connector authorizes over OAuth, so no passwords are stored. It runs on the free plan (40 requests/week), then Pro at $16/month. Jarvis confirms before sending invites or writing to Notion, so nothing happens without your sign-off.

A typical chain starts in Gmail: Jarvis reads the thread you have open, extracts the people, the proposed time, and the topic. It then creates a Google Calendar event, inviting the sender and anyone CC'd, with a title and description drawn from the email. Finally it writes to Notion — a new page in your meetings database, a row in a tracker, or a block under an existing project page — linking back to both the email and the calendar invite. You trigger all three steps with one sentence from the floating bar. Jarvis shows you the drafted invite and the Notion entry before committing, so you stay in control of every write.

The first time you run this, you might specify "30 minutes, my Client Calls Notion database, my work calendar." Jarvis stores those as persistent, user-controlled preferences. Next time you just say "set this up," and it reuses your defaults — meeting length, attendee conventions, the exact Notion destination. Memory lives under your control: you can view, edit, or delete what Jarvis remembers from settings. This is what separates a real chain from copy-paste: Jarvis carries context from the Gmail step into the Calendar step into the Notion step, so the CRM entry already knows the attendee, the time, and the source thread without you restating any of it.

Integrations