WorkerKit

AI workers for Executive Assistant

AI workers for executive assistants that guard the calendar, triage the exec inbox, and prep briefs so you stay ahead of a packed schedule. Connect Google Calendar, Gmail, and Drive, then let the firewall keep every read scoped and logged.

Browse every worker kit

What is a Executive Assistant AI worker?

An Executive Assistant AI worker is an AI agent set up to run one assistant job unattended, such as guarding an executive's calendar, triaging their inbox, or prepping meeting briefs. It typically touches Google Calendar and Gmail or Outlook, Google Drive files, and Slack, and only the calendars, threads, and folders you approve, with the firewall gating every read.

What these workers do

Guard the executive's calendar

Watch the exec's Google Calendar for double-bookings and back-to-backs with no gap, and flag conflicts so you can fix them early.

Triage the executive inbox

Sort the exec's Outlook into needs-a-reply, FYI, and scheduling, surfacing only what truly needs their attention today.

Prep a pre-meeting brief

Before each meeting, gather recent email and files for the attendees into a one-page brief so the exec walks in ready.

Draft scheduling replies

Draft responses to meeting requests based on the exec's availability, leaving each for you to review and send, never sending itself.

How a Executive Assistant AI worker runs

What an executive assistant worker connects to

An executive assistant worker connects to the accounts you manage for an executive. Point it at Google Calendar and Gmail or Outlook for the schedule and inbox, Google Drive for documents, and Slack for coordination. Because you handle a principal's private data, you approve exactly which calendars, threads, and folders it can open.

When it runs

What stays under your control

The firewall protects the principal's data. You can keep the worker read-only so it triages and drafts without sending, redact sensitive details before they reach the model, and block specific contacts. Per-label scope keeps it inside the parts of the inbox you name, and the audit trail records every thread and event it opened. Because it runs on a token you control, you can narrow or revoke its access at any time.

Executive Assistant questions, answered.

Can an executive assistant AI worker send email as the exec?

Only if you grant send access, and most assistants keep it draft-only. The worker drafts scheduling and inbox replies and leaves them for you to review and send, so the executive's voice stays in human hands. You can block specific contacts, cap draft volume, and revoke access anytime, with every action recorded in the audit trail for accountability.

How does it protect the executive's private data?

An executive assistant worker runs behind the firewall, which redacts sensitive details before they reach the model and confines the worker to the calendars, threads, and folders you approve. Private contacts can be blocked, and anything outside the approved scope stays invisible. Every read is logged, so you keep a full record of what the worker accessed on the exec's behalf.

Can it manage the calendar without me?

It can watch the calendar and flag conflicts, but it stays read-only unless you grant write access, so bookings remain your call. When you do allow it, the firewall limits writes to the calendars you approve, and it can propose slots for you to confirm. Every event it reads or changes is recorded, and you can revoke that access instantly.

Will it see personal email mixed with work?

Only the labels or folders you scope in. An executive assistant worker reaches the parts of the inbox you approve and nothing else, so you can point it at work threads while personal mail stays hidden. It can stay read-only, sensitive contacts can be blocked, and the audit trail records every message it opened for the executive.