# Activity Logs

Collects meeting activity logs from your Zoom organization, providing detailed information about user actions during zoom meetings including starting/ending meetings, leaving/joining meetings, recordings etc.

## Details
Monad uses the `activity_time` field to track the timestamp of the most recent record processed, allowing incremental syncing of new activity logs. On initial run, the connector fetches historical data from up to 5 months ago and then transitions to regular monthly processing, fetching logs in one-month chunks to ensure comprehensive coverage.

## Requirements
1. Confirm your account has [Zoom Reporting](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0060623) enabled
   1. Specifically for Meeting Activity Logs you need to Contact Zoom Support to enable the meeting audit trail log feature on your account.
2. The zoom app will be created under a personal account. Ensure that the role assigned to the user creating the app has the following permissions assigned to it.
   1. Navigate to **User Management > Roles** and edit the Admin role.
      1. Navigate to **Reports** and enable `View` permissions for the following:
         1. Usage reports
         2. User activity reports
            1. Meeting Activity Logs
3. Follow the instructions to build an [Server-to-Server OAuth Zoom app](https://developers.zoom.us/docs/internal-apps/create/#steps-to-create-a-server-to-server-oauth-app) (not to be confused with the OAuth app).
4. After you name the app, you will be presented with the following information. Save this information for use when configuring the connector
   1. Account ID
   2. Client ID
   3. Client Secret
5. Add the following scopes to the app (do not select Optional):
   1. View user meeting activity logs
      `report:read:meeting_activity_log:admin`

## Related Articles
- [Zoom API Documentation - Activity Logs](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/reportMeetingactivitylogs)
- [Zoom OAuth Implementation Guide](https://developers.zoom.us/docs/integrations/oauth/)

## Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.

#### Settings

| Setting | Type | Required | Description |
|---------|------|----------|-------------|
| Account ID | string | Yes | The identifier for the zoom account. |
| Backfill Start Time | string | No | The date to start fetching data from. If not specified, no past records will be fetched. |
| API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See [API Rate Limiting](../../../guides/rate-limiting) for the field format, limits, and how to choose a value. |

#### Secrets

| Secret | Type | Required | Description |
|---------|------|----------|-------------|
| Client ID | string | yes | The client id is the provided public identifier for an app. |
| Client Secret | string | yes | The client secret is known only to the application and the authorization server. |

## Limitations
1. This connector works with Pro plan or higher accounts.
2. Accounts must have [Zoom Reporting enabled](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0060623).
3. The source connector is restricted by [rate limits](https://developers.zoom.us/docs/api/rest/rate-limits/).
4. This input will poll once an hour to avoid rate limits.

## Sample Record

```json
{
    "meeting_number": "847 256 3921",
    "activity_time": "2025-12-08T15:42:33Z",
    "operator": "Sarah Johnson",
    "operator_email": "sarah.johnson@example.com",
    "activity_category": "Participant Joined",
    "activity_detail": "Participant Joined"
}
```