---
title: Meetings
subtitle: >-
  A Meeting activity represents a calendar event synced from Google Calendar or
  Microsoft Outlook, or created manually
---

A Meeting activity represents a calendar event synced from Google Calendar or Microsoft Outlook, or created manually.

A meeting activity can have the following statuses:
- `upcoming` if the meeting is in the future
- `in-progress` if the meeting is currently in progress
- `completed` if the meeting happened and has ended
- `canceled` if the meeting was deleted from all synced calendars, all participants that exist as contacts on a lead were removed from the meeting, or the meeting was moved to an "all day" event after it was synced on a lead page
- `declined-by-lead` if at least one contact on the lead that is a part of the attendees list declined the meeting, and no other contacts on the lead accepted the meeting
- `declined-by-org` if all Close users on the meeting declined to attend

Each contact in the `attendees` array can have the following statuses:
- `noreply` if the attendee has yet to reply to the meeting invite
- `yes` if the attendee has replied yes
- `no` if the attendee has replied no
- `maybe` if the attendee has replied maybe

Provider calendar information fields are also available. See [Meeting Search](/api/resources/activities/meetings):
- `provider_calendar_event_id` - the provider event ID the meeting was synced from
- `provider_calendar_ids` - the provider calendar IDs the meeting was synced from
- `provider_calendar_type` - either `"google"` or `"microsoft"`

The `is_recurring` field will be `true` if a meeting is a recurring meeting on your Google Calendar.

The following date and time fields are available:
- `date_created` and `date_updated` - when the meeting object was created and last updated in Close
- `starts_at` and `ends_at` - when the meeting event starts and ends
- `activity_at` - determines where the meeting shows up in the activity timeline, set to `starts_at` by default

To add Meeting notes to an existing Meeting activity, use the `user_note_html` field. Notes should be formatted as [rich text](/api/overview/rich-text) and can include links, images, and other rich-text elements.

Meetings may be assigned a custom user-defined outcome via the `outcome_id` field. See [Outcomes](/api/resources/outcomes) to learn more.

#### Meeting transcripts

Meeting transcripts can be accessed using this API but are not loaded by default. To load transcripts, use the [`_fields`](/topics/fields/) parameter with `transcripts` value. The `transcripts` field is an array of objects for each Close Notetaker bot that joined the meeting. Typically, there will be only one transcript though. The transcripts are ordered by the time bots joined the meeting.

Example transcript in response:

```json
{
  "transcripts": [
    {
      "utterances": [
        {
          "speaker_label": "John Lead",
          "speaker_side": "contact",
          "start": 0.1,
          "end": 1.2,
          "text": "Hey, what's up? How is it going?"
        },
        {
          "speaker_label": "Jane User",
          "speaker_side": "close-user",
          "start": 1.3,
          "end": 2.4,
          "text": "Hey John, I'm doing great. How about you?"
        }
      ],
      "summary_text": "Summary text",
      "summary_html": "<p>Summary text</p>"
    }
  ]
}
```