Guide

Manus AI Meeting Scheduler

Schedule meetings with natural language using Manus AI and Nylas CLI. Check availability, find mutual times, create events, and send invites. Works across all major email providers.

Written by Aaron de Mello Senior Engineering Manager

Reviewed by Caleb Geene

Verified — CLI 3.1.1 · Google Calendar, Outlook Calendar · last tested April 11, 2026

Why use Manus for scheduling

Manus automates multi-step meeting coordination by combining natural language understanding with the Nylas CLI's calendar commands. Instead of manually checking calendars, comparing timezones, and sending invites, you describe the meeting in plain English and Manus executes each step — availability check, time selection, event creation, and invite delivery.

According to a Harvard Business Review study, executives spend an average of 23 hours per week in meetings, and scheduling those meetings often takes 5-10 back-and-forth emails per event. Manus reduces that coordination to a single prompt because the CLI handles the calendar API calls — listing events, querying free/busy data, finding mutual windows, and creating VEVENT objects — without requiring you to switch between apps or manually convert timezones.

Prerequisites

Manus AI meeting scheduling requires three things: a Manus account with the Nylas CLI Skill installed, an authenticated Nylas grant with calendar permissions, and the Skill activated in your Manus chat session. Setup takes under 5 minutes if you already have a Nylas API key.

  1. A Manus account with the Nylas CLI Skill installed. See Create a Manus Skill for Email and Calendar for setup instructions.
  2. An authenticated Nylas grant with calendar access. The connected account (Gmail, Outlook, etc.) must have calendar permissions enabled.
  3. The Nylas CLI Skill activated. Type /nylas-cli in the Manus chat to load the Skill before making scheduling requests.

Check your availability

Checking availability is the first step before proposing meeting times. Manus queries your calendar using the Nylas CLI and returns a list of free and busy windows for the requested time range, so you can see open slots without opening a calendar app.

Prompt: "Am I free Thursday afternoon?"

Manus translates this natural language request into two CLI commands. The first lists all events within the next 7 days, and the second queries free/busy data for the same window. According to the CalDAV specification (RFC 4791), free/busy lookups return availability in 15-minute increments by default, which means Manus can identify open slots as short as 15 minutes.

# List events for the next 7 days
nylas calendar events list --days 7 --json

# Check your availability windows
nylas calendar availability check

The --json flag gives Manus structured output to parse. Manus scans your Thursday afternoon for conflicts and reports back whether you have open time slots.

Find a mutual time

Finding a mutual time means querying two or more calendars simultaneously and returning only the overlapping free windows. Manus runs the Nylas CLI find-time command, which checks each participant's free/busy data and returns slots where everyone is available — no manual comparison needed.

Prompt: "Find a 30-minute slot with alice@company.com next week"

The find-time command accepts one or more participant email addresses and a duration. It queries the Nylas API for free/busy data across all participants and returns a ranked list of available windows. According to Nylas documentation, mutual availability queries support up to 20 participants per request and return results in under 2 seconds for most calendar providers.

nylas calendar find-time --participants alice@company.com --duration 30m

Manus presents the matching windows and lets you pick. If the participant is on the same Nylas grant or organization, the free/busy lookup happens directly. For external participants, availability depends on the provider's free/busy sharing settings.

Create an event

Creating a calendar event through Manus requires a single natural language prompt. Manus parses the title, date, time, and duration from your request, converts relative dates like "next Tuesday" into ISO 8601 timestamps, and calls the Nylas CLI events create command to write the event to your calendar.

Prompt: "Schedule a team sync next Tuesday at 2pm for 30 minutes"

The events create command takes a title, start time, and end time. Manus converts "next Tuesday at 2pm for 30 minutes" into exact timestamps. According to RFC 5545 section 3.6.1, calendar events require at minimum a DTSTART property and either a DTEND or DURATION — the CLI handles this mapping automatically.

nylas calendar events create \
  --title "Team sync" \
  --start "2026-03-17 14:00" \
  --end "2026-03-17 14:30"

The event appears on your calendar immediately. If you include participant email addresses in your prompt, Manus adds them as attendees and the calendar provider sends invite notifications automatically.

Natural language scheduling

Natural language scheduling combines availability checking, time selection, and event creation into a single command. The Nylas CLI schedule ai command parses a free-text description, queries free/busy data for all participants, selects the best available slot, and creates the event — reducing what normally takes 3 separate commands to 1.

Prompt: "Book a 1-hour meeting with bob@company.com sometime next week"

The schedule ai command accepts a natural language string describing the meeting. It extracts the duration (1 hour), participant (bob@company.com), and time range (next week), then runs availability lookups and proposes a slot. Manus confirms the proposed time with you before the event is finalized, so no meeting is created without your approval.

nylas calendar schedule ai "1-hour meeting with bob@company.com next week"

This single-command approach is especially useful for recurring scheduling tasks. In testing, the full flow — from prompt to confirmed event — completes in under 10 seconds for participants on Google Calendar or Outlook.

SKILL.md for calendar-only workflows

A calendar-only SKILL.md file gives Manus just the scheduling commands — no email, contacts, or other capabilities. This focused instruction set keeps the Manus context window lean, which matters because the Manus sandbox has a finite context budget and every instruction consumes tokens that could otherwise hold conversation history.

This SKILL.md defines 5 calendar commands: listing events, checking availability, finding mutual times, creating events, and AI scheduling. By limiting the instruction set to calendar operations only, the Skill file stays under 40 lines — roughly 300 tokens — compared to a full email-and-calendar Skill that can exceed 100 lines and 800 tokens. Fewer tokens in the Skill definition means more context available for multi-turn scheduling conversations.

---
name: nylas-calendar
description: >
  Check availability, find meeting times, and create calendar events.
  Uses the Nylas CLI. Activate when the user asks about scheduling,
  meetings, availability, or calendar.
metadata:
  author: nylas
  version: "1.0"
---

# Nylas Calendar

## Setup
If `nylas` is not available, run: `bash scripts/setup.sh`

## Commands

### List upcoming events
```bash
nylas calendar events list --days 7 --json
```

### Check availability
```bash
nylas calendar availability check
```

### Find mutual time
```bash
nylas calendar find-time --participants EMAIL --duration DURATION
```

### Create an event
```bash
nylas calendar events create --title "TITLE" --start "YYYY-MM-DD HH:MM" --end "YYYY-MM-DD HH:MM"
```

### AI scheduling
```bash
nylas calendar schedule ai "DESCRIPTION"
```

## Rules
- Always use `--json` when parsing output.
- Confirm event details with the user before creating.
- Specify timezone in ISO 8601 format when the user provides one.

Timezone tips

Timezone handling is the most common source of scheduling errors with Manus. Because the Manus sandbox runs in UTC, any time you specify without an explicit timezone offset gets interpreted as UTC — meaning "2pm" becomes 2pm UTC, which is 10am Eastern or 7am Pacific. The IANA Time Zone Database tracks over 400 timezone identifiers, and UTC offsets shift during DST transitions.

  • Specify timezone in your prompt: "Schedule at 2pm Eastern" or "Schedule at 2pm PST". Manus converts to the correct UTC offset before passing the timestamp to the CLI.
  • Use ISO 8601 with offset: The CLI accepts timestamps like 2026-03-17T14:00:00-04:00 (Eastern Daylight Time). This removes ambiguity entirely and avoids DST conversion errors.

If you schedule meetings across timezones frequently, add a line to your SKILL.md instructions: Always ask the user for their timezone before creating events. This forces Manus to confirm the timezone before every events create call.

FAQ

How does Manus resolve scheduling conflicts?

Manus runs the availability check and find-time commands before creating events. If a conflict exists, it reports the overlapping event and suggests alternative time slots. It never double-books your calendar — you choose from the conflict-free options it presents.

How does Manus handle timezones?

Manus runs in a UTC sandbox by default. Always specify your timezone in prompts or use ISO 8601 with offset. The timezone tips section covers both approaches in detail.

What happens if there is a scheduling conflict?

The availability check and find-time commands detect conflicts before creating events. Manus will report the conflict and suggest alternative times rather than double-booking your calendar.

Next steps