Scheduling from the command line saves time when you're already in the terminal. Here's how nylas calendar analyze works.

The nylas calendar analyze command breaks down your calendar data into actionable stats: total meeting hours, busiest day of the week, average meeting duration, recurring vs one-off ratio, and focus-time gaps. Specify --days to set the analysis window.

Examples

Analyze meeting time breakdown for last 30 days:

nylas calendar analyze --days 30

Find your busiest day this week:

nylas calendar analyze --days 7

Export stats as JSON for a dashboard:

nylas calendar analyze --days 90 --json

Syntax

nylas calendar analyze [--days N] [--json]

How It Works

Calendar APIs are notoriously inconsistent across providers. Google Calendar uses RFC 5545 recurrence rules, Outlook uses its own format, and Exchange has yet another. The Nylas CLI normalizes all of this behind a consistent interface.

Common Issues

Analysis shows 0 meetings
Check that you're authenticated with the right account. Run nylas auth whoami to verify.

Slow analysis on large calendars
Reduce the --days window. Analyzing 365 days of data can take 10-15 seconds on busy calendars.

Full docs: nylas calendar analyze reference — all flags, advanced examples, and troubleshooting.

All commands: Nylas CLI Command Reference

Get started: brew install nylas/nylas-cli/nylas — other install methods