ai-scheduler

AI Scheduler (Zoom + AgentMail)

Use the bundled script to (a) create a Zoom meeting via API, and/or (b) send an AgentMail email with an .ics invite attachment and the standard invitation body.

Style + confirmation rules

• Keep the email professional and minimal.
• Always show a full email preview (subject + body) before sending, then confirm (before sending) the host email (From), meeting time (with timezone), and participants (To/CC). The script prints a full email body preview before sending (even with --yes).
• Subject rule: if there is exactly 1 --to recipient, use <PREFIX> <TO_NAME>: <TOPIC> (prefer the display name if provided). <PREFIX> must be provided via env AGENTMAIL_SUBJECT_PREFIX (loaded from .env.scheduler) or --subject-prefix. The script compacts <TOPIC> to at most 5 words.
• To disable the prefix, pass --no-subject-prefix (subject becomes <TO_NAME>: <TOPIC> for a single recipient, else <TOPIC>).
• To force the subject to be just the topic (no <TO_NAME>:), pass --subject-topic-only (works with or without a subject prefix).
• Zoom meeting title rule: most punctuation is stripped/simplified for the Zoom meeting title sent to the Zoom API (email subject/body keep your original punctuation).

Required inputs

• Topic (used for the Zoom meeting title and email subject)
• Optional chat topic (used in the body as the meeting topic)
• Start date/time + timezone (e.g. 2026-03-15 19:00, America/New_York)
• Duration in minutes
• Participants (--to and optional --cc, comma-separated). You can use either:
  • plain emails: --to "[email protected]"
  • display name + email: --to "Ry <[email protected]>"
• Host display name (default: Ryan Z. Nie)
• Host email (optional; set AGENTMAIL_HOST, otherwise defaults to AGENTMAIL_INBOX_ID)

Credentials (do not paste secrets into chat)

• Zoom Server-to-Server OAuth:
  • ZOOM_ACCOUNT_ID
  • ZOOM_CLIENT_ID
  • ZOOM_CLIENT_SECRET
• AgentMail:
  • AGENTMAIL_API_KEY
  • AGENTMAIL_INBOX_ID (required; used as the From/host email)

Preferred: set env vars in the environment running the script.

Optional: put env vars in .env.scheduler (default), or pass a custom path via --env-file. The script reads the env file and only fills missing env vars. Treat the values below as placeholders and keep the real values in .env.scheduler.

ZOOM_ACCOUNT_ID=...
ZOOM_CLIENT_ID=...
ZOOM_CLIENT_SECRET=...
AGENTMAIL_API_KEY=...
[email protected]
AGENTMAIL_INBOX_DISPLAY_NAME=Ryan Nie's AI Agent
AGENTMAIL_HOST_NAME=Ryan Nie's AI Agent
[email protected]
AGENTMAIL_SUBJECT_PREFIX=Ryan +

Run

Create a meeting via Zoom API, then email an invite. Run from this skill directory:

. .venv_agentmail/bin/activate
.venv_agentmail/bin/python scripts/schedule_zoom_and_send_invite.py \
  --topic "AgentMail" \
  --chat-topic "<Topic>" \
  --to "[email protected]" \
  --cc "[email protected]" \
  --start "2026-03-15 19:00" \
  --tz "America/New_York" \
  --duration 30

Reuse an existing Zoom meeting (skip Zoom API) and just send the invite email. Run from this skill directory:

. .venv_agentmail/bin/activate
.venv_agentmail/bin/python scripts/schedule_zoom_and_send_invite.py \
  --topic "AgentMail" \
  --chat-topic "<Topic>" \
  --to "[email protected]" \
  --cc "[email protected]" \
  --start "2026-03-15 19:00" \
  --tz "America/New_York" \
  --duration 30 \
  --existing-join-url "<zoom join url>" \
  --existing-meeting-id <zoom meeting id> \
  --existing-passcode "<passcode>"

Standard body template

The invite email body must not be hardcoded. The script renders the email body by reading references/body-template.md and filling placeholders with your inputs (topic, host, participants, when, join URL, meeting ID, passcode, disclaimer).

• See references/body-template.md for the exact text template.