Demo · 67 seconds

“Are you free next week?”, answered

The back and forth between inbox and calendar is done in one request, across two signed-in tools, and nothing is sent without you.

  • Gmail
  • Google Calendar

The request

Laura wants to grab coffee next week. Her email is in my Gmail, the subject is “Coffee next week?”. Check my Google Calendar, pick a slot that works for both of us, put a hold in my calendar, and draft a reply to her in Gmail. Don’t send it. Keep Gmail and Calendar in their own tabs.

Where it starts: An empty new tab. Gmail and Google Calendar are signed in, and Laura’s email is in the inbox.

What happens

  1. The companion opens Gmail and reads Laura’s email: a 45-minute coffee on Tuesday or Wednesday next week, any time between 13:00 and 17:00.
  2. It opens Google Calendar. Tuesday is full; Wednesday 18 November is free from 14:00 to 16:00.
  3. It puts a hold called “Hold: Coffee with Laura” in the calendar from 14:30 to 15:15, with no guests, so no invite goes out.
  4. Back in Gmail, it writes the reply offering Wednesday from 14:30 to 15:15, and leaves it as a draft.
  5. It replies with what it found and did, and says the hold can be renamed and Laura added once she confirms.

What it shows

The back and forth between inbox and calendar is done in one request, across two signed-in tools, and nothing is sent without you.

What the video says

“You know those emails? Hey, are you free next week? And then you’re flipping between your inbox and your calendar, hunting for a gap.” “In Apex, I just ask.” “It opens the email in my Gmail. My real inbox, already signed in. And reads what Laura’s asking for.” “Then it hops over to my calendar. Tuesday’s a mess… but Wednesday has a gap. So it puts a hold right there.” “Back in Gmail, it writes the reply with that exact time. As a draft. Nothing goes out until I say so.” “Inbox, calendar, and back again, in under a minute. That’s not a chatbot answering a question. That’s the job, done.”

This is a screen recording in real, signed-in accounts, with nothing mocked. The emails, events and receipts in them were set up for the demo, so the people in them are examples. Long waits are cut or sped up, and a chip in the corner says so while it is sped up. Product names and marks belong to their owners; Apex is not affiliated with them.

Try it yourself

Open the site in Apex, open the companion’s panel and type the request in your own words. The companion asks before anything that matters, and it is never allowed to type passwords or card details. Getting started takes a few minutes.

More like this

An expense report from your inbox

“I forwarded five receipts to myself in Gmail today. Put them in a new Google Sheet called Expenses November with the date, merchant, amount and currency, convert the dollar ones to euros with today’s rate from xe.com, and add a total in euros. Keep Gmail, xe and the sheet each in their own tab.”

Meeting prep from your calendar

“Look at my Google Calendar for tomorrow. For each meeting, look up the company on its own website, then write me a short prep brief in a new Google Doc called Meeting prep. Keep each site in its own tab.”

Planning a team trip

“Tom asked about a team trip to Lisbon. His email is in my Gmail, the subject is “Lisbon offsite?”. Check in my Google Calendar which weekend I’m free, look up flights on Google Flights and a hotel on Booking.com for those dates, and draft a reply to Tom in Gmail with the dates and the cost per person. Don’t send it. Keep every site in its own tab.”

All use cases

Come make something.

Apex is free and open source, for Mac and Windows. Download it, pick a companion, and build the first thing you’ve been missing.

Download Apex Free and open source. Runs on Claude with your own Anthropic API key. How to get started