slice icon Context Slice

Calendly Scheduled Events

Event Data Structure

Each event includes:

  • uuid - Unique identifier
  • name - Event type name (e.g., "30 Mins", "Intro to Sauna")
  • startTime / endTime - ISO 8601 timestamps in UTC
  • durationMinutes - Meeting length
  • location - Meeting location with type and joinUrl
  • invitees - Array of people who booked (see below)

Invitee Object

{
  "name": "Jane Smith",
  "email": "jane@example.com",
  "timezone": "America/Los_Angeles",
  "status": "active",
  "questionsAndAnswers": [
    {
      "question": "Share any thoughts with us...",
      "answer": "Interested in learning about automation"
    }
  ]
}

Understanding Form Responses

Critical: The questionsAndAnswers array contains responses to booking form questions that YOU (the Calendly host) configured. These are NOT meeting agendas or topics.

When presenting form responses:

  • ✅ Summarize in third person: "He mentions that he...", "She's looking to..."
  • ✅ Present as context about the person, not the meeting topic
  • ✅ Extract the key intent succinctly
  • ❌ Don't quote verbatim—summarize instead
  • ❌ Don't say "The meeting is about X" based on form responses
  • ❌ Don't editorialize or add your interpretation

Location Types

  • zoom - Zoom meeting (has joinUrl)
  • google_meet - Google Meet (has joinUrl)
  • microsoft_teams - Teams meeting (has joinUrl)
  • phone_call - Phone call
  • physical - In-person location

Time Handling

All times from the API are in UTC (ISO 8601 format). You MUST convert to the user's local timezone before presenting. Check their profile or ask explicitly.

Example: 2024-01-15T20:00:00Z is 8 PM UTC, which is:

  • 12:00 PM in San Francisco (PST/PDT)
  • 3:00 PM in New York (EST/EDT)
  • 8:00 PM in London (GMT)

Presentation Format

Use dividers between events for readability:

Tomorrow (Thu Jan 15)

12:00 PM — 30 Mins — Olly (olly@example.com)
He wants to preview the team meeting UI on Discord.

---

1:00 PM — Intro to Sauna — Sam Skinner (sam@example.com)
He's looking for help with business tasks he can't get around to.

---

3:00 PM — Intro to Sauna — Jane Doe (jane@example.com)
(No notes submitted)

Key elements:

  1. Date header with day of week
  2. Time in user's local timezone (AM/PM)
  3. Event type name
  4. Invitee name and email
  5. Succinct summary of form response in third person (or "No notes submitted")
  6. --- divider between each event