Zoom Integration for Elastic

Zoom is a unified communications platform that provides meetings, webinars, phone, team chat, and Zoom Rooms. The Zoom integration for Elastic enables you to collect Zoom event and audit data so you can monitor user activity, investigate security incidents, and analyze platform usage in Elastic.

This integration collects data using two complementary methods:

• Webhook: a real-time HTTP listener that receives event notifications pushed by Zoom (meeting, webinar, recording, user, account, phone, team chat, and Zoom Room events).
• REST API: a periodic poll of the Zoom REST API to collect the sign in / sign out activity report, the operation logs report, and the meeting_activity logs report for an account.

Elastic Managed integrations are only supported on Elastic Cloud Serverless and Elastic Cloud Hosted deployments. An Elastic Managed integration lets you ingest data from a cloud source while avoiding the orchestration, management, and maintenance associated with standard ingest infrastructure. Elastic runs the collector for you, so you can focus on your data instead of the infrastructure that collects it.

For more information, refer to Elastic Managed integrations and the Elastic Managed integrations FAQ.

• The activity data stream uses the Zoom REST API GET /report/activities endpoint and requires a Zoom Pro (or higher) plan.
• The operation data stream uses the Zoom REST API GET /report/operationlogs endpoint and requires a Zoom Pro plan or above.
• The meeting_activity data stream uses the Zoom REST API GET /report/meeting_activities endpoint. The meeting audit trail log feature must be enabled for the account by Zoom Support.

The webhook data stream creates an HTTP listener that accepts incoming webhook callbacks from Zoom. The Elastic Agent running this integration must be reachable from the internet so that Zoom can connect to it. Zoom requires that webhooks are delivered over HTTPS, so you must either configure the integration with a valid TLS certificate or place a reverse proxy that terminates TLS in front of the integration. Incoming events are then routed to the appropriate ingest pipeline based on the Zoom event type.

The activity, operation and meeting_activity data streams poll the Zoom REST API using Server-to-Server OAuth. On each interval, they request records within a date window (a maximum of one month per request) and paginate through the results.

The Zoom integration collects the following data:

• webhook: real-time Zoom event notifications, including account, team chat (channel and message), meeting, phone, recording, user, webinar, and Zoom Room events.
• activity: account-wide sign in and sign out activity logs from the Zoom REST API reports endpoint. Note that the API does not provide data for failed sign-in or authentication attempts, so those logs will not be available here.
• operation: account-wide admin and user operation logs from the Zoom REST API reports endpoint, such as adding a user, changing account settings, or deleting a recording.
• meeting_activity: meeting activity logs from the Zoom REST API reports endpoint, such as a meeting being created or started, a user joining or leaving, in-meeting chat, remote control, and a meeting ending.

Integrating Zoom with Elastic SIEM provides centralized visibility into collaboration and administrative activity:

• Webhook events enable real-time monitoring across meetings, recordings, users, and account changes.
• The activity report provides an account-wide sign in / sign out audit trail for investigating user access and anomalous logins.
• The operation logs report tracks admin and user operations for auditing configuration changes and detecting unauthorized actions.
• The meeting_activity logs report provides a meeting-level audit trail of meeting lifecycle and participant activity — meetings being created, started, and ended, participants joining and leaving, in-meeting chat, and remote control — helping you reconstruct what happened in a specific meeting, monitor meeting usage, and support compliance investigations.

1. Create a Webhook-only app in the Zoom App Marketplace by following the Zoom webhook documentation.
2. Add the event types you want to receive and set the event notification endpoint URL to the public HTTPS address where this integration is reachable.
3. Note the Secret Token generated by Zoom. It is used for CRC endpoint validation and to verify the authenticity of incoming events.

1. Create a Server-to-Server OAuth app in the Zoom App Marketplace by following the Server-to-Server OAuth documentation.
2. Record the app's Account ID, Client ID, and Client Secret.
3. Add the report:read:admin scope (or the granular report:read:user_activities:admin, report:read:operation_logs:admin & report:read:meeting_activity_log:admin scopes) to the app and activate it. A Zoom Pro plan or above is required.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

Elastic Agent is required to receive the Zoom webhook callbacks or to poll the Zoom REST API, and to ship the data to Elastic, where the events are then processed via the integration's ingest pipelines.

1. In the top search bar in Kibana, search for Integrations.

2. In the search bar, type Zoom.

3. Select the Zoom integration from the search results.

4. Select Add Zoom to add the integration.

5. Enable and configure only the collection methods which you will use.

   • To Collect Zoom logs via Webhook, you'll need to:

     • Configure the Listen Address, Listen Port, and Webhook path where the integration accepts requests.
     • Optionally enable CRC validation and provide the Zoom Secret Token, and/or configure a custom header to verify incoming requests.
     • Provide a valid TLS certificate (or front the integration with a TLS-terminating reverse proxy), since Zoom requires HTTPS.

   • To Collect Zoom logs via REST API, you'll need to:

     • Configure the Account ID, Client ID, and Client Secret of your Server-to-Server OAuth app.
     • Adjust the integration configuration parameters if required, including the Interval and Initial Interval (lookback), to enable data collection.

6. Select Save and continue to save the integration.

1. In the top search bar in Kibana, search for Dashboards.
2. In the search bar, type Zoom.
3. Select a dashboard for the dataset you are collecting, and verify the dashboard information is populated.

For help with Elastic ingest tools, check Common problems.

The REST API data streams (activity, operation, and meeting_activity) query Zoom's Report endpoints, which are classified as Heavy APIs. Zoom enforces both a per-second (QPS) limit and a daily request quota, and both are shared across every app and user on the account, as well as across all of the Report data streams in this integration:

To keep the Report data streams within this shared budget, each REST API data stream has client-side rate limiting enabled by default (Rate Limit and Rate Limit Burst in the data stream settings). The default values are conservative so that the streams can run together without exhausting the account quota, which matters most during the initial backfill when many requests are made.

If you hit an HTTP 429 Too Many Requests response, or you want to tune throughput, adjust these settings per data stream:

• Reduce the rate (lower the Rate Limit, for example to 0.05) if you are seeing 429 errors, if other applications share the same Zoom account quota, or if the daily quota is being consumed too quickly. A daily-limit 429 is only cleared at 00:00 UTC, so it is better to run slower than to be locked out.
• Increase the rate (raise the Rate Limit) if you are on a Business+ plan, run fewer Report data streams, or need the initial backfill to complete faster. Keep the combined rate of all enabled Report data streams below your plan's per-second limit.

You can also reduce the total number of requests by increasing the Page Size (up to Zoom's maximum of 300), since fewer, larger pages consume less of the shared quota.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

This is the webhook data stream. It collects real-time event notifications pushed by Zoom over an HTTP endpoint.

{
    "@timestamp": "2019-07-01T17:03:04.527Z",
    "agent": {
        "ephemeral_id": "25caa0a1-dfe6-4499-8945-78d3f7b50b5c",
        "id": "a2a6d6ce-cd38-4a30-8877-bf698b0d346b",
        "name": "docker-fleet-agent",
        "type": "filebeat",
        "version": "8.8.1"
    },
    "data_stream": {
        "dataset": "zoom.webhook",
        "namespace": "ep",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "a2a6d6ce-cd38-4a30-8877-bf698b0d346b",
        "snapshot": false,
        "version": "8.8.1"
    },
    "event": {
        "action": "account.updated",
        "agent_id_status": "verified",
        "category": [
            "iam"
        ],
        "dataset": "zoom.webhook",
        "ingested": "2023-06-22T16:37:08Z",
        "kind": [
            "event"
        ],
        "original": "{\"event\":\"account.updated\",\"payload\":{\"account_id\":\"abKKcd_IGRCq63yEy673lCA\",\"object\":{\"account_alias\":\"MH\",\"account_name\":\"Michael Harris\",\"id\":\"eFs_EGRCq6ByEyA73qCA\"},\"old_object\":{\"account_alias\":\"\",\"account_name\":\"Mike Harris\",\"id\":\"eFs_EGRCq6ByEyA73qCA\"},\"operator\":\"theoperatoremail@someemail.com\",\"operator_id\":\"iKoRgfbaTazDX6r2Q_eQsQL\",\"time_stamp\":1562000584527}}",
        "timezone": "+00:00",
        "type": [
            "user",
            "change"
        ]
    },
    "input": {
        "type": "http_endpoint"
    },
    "observer": {
        "product": "Webhook",
        "vendor": "Zoom"
    },
    "related": {
        "user": [
            "iKoRgfbaTazDX6r2Q_eQsQL",
            "eFs_EGRCq6ByEyA73qCA"
        ]
    },
    "tags": [
        "preserve_original_event",
        "zoom-webhook",
        "forwarded"
    ],
    "user": {
        "changes": {
            "full_name": "Michael Harris",
            "name": "MH"
        },
        "email": "theoperatoremail@someemail.com",
        "id": "iKoRgfbaTazDX6r2Q_eQsQL",
        "target": {
            "full_name": "Mike Harris",
            "id": "eFs_EGRCq6ByEyA73qCA"
        }
    },
    "zoom": {
        "account": {
            "account_alias": "MH",
            "account_name": "Michael Harris"
        },
        "master_account_id": "abKKcd_IGRCq63yEy673lCA",
        "old_values": {
            "account_name": "Mike Harris",
            "id": "eFs_EGRCq6ByEyA73qCA"
        },
        "operator": "theoperatoremail@someemail.com",
        "operator_id": "iKoRgfbaTazDX6r2Q_eQsQL",
        "sub_account_id": "eFs_EGRCq6ByEyA73qCA"
    }
}

This is the activity data stream. It collects sign in / sign out activity logs from the Zoom REST API.

{
    "@timestamp": "2026-07-01T10:00:00.000Z",
    "agent": {
        "ephemeral_id": "bccd735f-96cf-4486-b3dd-51ed5c2f3103",
        "id": "93a4ccfb-5f31-4449-9f9c-25acc67912b9",
        "name": "elastic-agent-61640",
        "type": "filebeat",
        "version": "8.19.0"
    },
    "data_stream": {
        "dataset": "zoom.activity",
        "namespace": "32155",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "93a4ccfb-5f31-4449-9f9c-25acc67912b9",
        "snapshot": false,
        "version": "8.19.0"
    },
    "event": {
        "action": "sign-in",
        "agent_id_status": "verified",
        "category": [
            "authentication",
            "session"
        ],
        "dataset": "zoom.activity",
        "ingested": "2026-07-02T14:08:25Z",
        "kind": "event",
        "outcome": "success",
        "type": [
            "start"
        ]
    },
    "input": {
        "type": "cel"
    },
    "related": {
        "ip": [
            "192.0.2.10"
        ],
        "user": [
            "alice@example.com"
        ]
    },
    "source": {
        "as": {
            "number": 64500,
            "organization": {
                "name": "Documentation ASN"
            }
        },
        "geo": {
            "city_name": "Las Vegas",
            "continent_name": "North America",
            "country_iso_code": "US",
            "country_name": "United States",
            "location": {
                "lat": 36.17497,
                "lon": -115.13722
            },
            "region_iso_code": "US-NV",
            "region_name": "Nevada"
        },
        "ip": "192.0.2.10"
    },
    "tags": [
        "forwarded",
        "zoom-activity"
    ],
    "user": {
        "email": "alice@example.com",
        "name": "alice@example.com"
    },
    "zoom": {
        "activity": {
            "client_type": "Browser",
            "client_version": "6.0.0.1000",
            "type": "Sign in"
        }
    }
}

This is the operation data stream. It collects admin and user operation logs from the Zoom REST API.

{
    "@timestamp": "2026-07-05T10:00:00.000Z",
    "agent": {
        "ephemeral_id": "c57755af-e69d-4f7d-ace8-918c91a349e8",
        "id": "ec73b436-1e5f-43c4-877e-870a10693449",
        "name": "elastic-agent-70306",
        "type": "filebeat",
        "version": "8.19.0"
    },
    "data_stream": {
        "dataset": "zoom.operation",
        "namespace": "85002",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "ec73b436-1e5f-43c4-877e-870a10693449",
        "snapshot": false,
        "version": "8.19.0"
    },
    "event": {
        "action": "Update",
        "agent_id_status": "verified",
        "category": [
            "configuration",
            "iam"
        ],
        "dataset": "zoom.operation",
        "ingested": "2026-07-06T12:16:55Z",
        "kind": "event",
        "type": [
            "change",
            "info"
        ]
    },
    "input": {
        "type": "cel"
    },
    "related": {
        "user": [
            "admin@example.com"
        ]
    },
    "tags": [
        "forwarded",
        "zoom-operation"
    ],
    "user": {
        "email": "admin@example.com",
        "name": "admin@example.com"
    },
    "zoom": {
        "operation": {
            "action": "Update",
            "category_type": "User",
            "operation_detail": "Activate User alice@example.com"
        }
    }
}

This is the meeting_activity data stream. It collects meeting activity logs from the Zoom REST API.

{
    "@timestamp": "2026-07-08T07:09:03.216Z",
    "agent": {
        "ephemeral_id": "6c3d442a-6d3a-4aee-9a00-822f09a5a140",
        "id": "c719dea7-dc28-43f1-9594-ff2feb858fea",
        "name": "elastic-agent-39398",
        "type": "filebeat",
        "version": "8.19.0"
    },
    "data_stream": {
        "dataset": "zoom.meeting_activity",
        "namespace": "87490",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "c719dea7-dc28-43f1-9594-ff2feb858fea",
        "snapshot": false,
        "version": "8.19.0"
    },
    "event": {
        "action": "Meeting Started",
        "agent_id_status": "verified",
        "dataset": "zoom.meeting_activity",
        "ingested": "2026-07-09T14:03:16Z",
        "kind": "event",
        "type": [
            "info"
        ]
    },
    "input": {
        "type": "cel"
    },
    "related": {
        "user": [
            "jillchill@example.com",
            "Jill Chill"
        ]
    },
    "tags": [
        "forwarded",
        "zoom-meeting_activity"
    ],
    "user": {
        "email": "jillchill@example.com",
        "name": "Jill Chill"
    },
    "zoom": {
        "meeting_activity": {
            "activity_category": "Meeting Started",
            "activity_detail": "Meeting Started",
            "meeting_number": "982 610 0285"
        }
    }
}

These inputs are used in this integration:

• http_endpoint
• cel

This integration uses the following APIs:

• activity: Get sign in / sign out activity report.
• operation: Get operation logs report.
• meeting_activity: Get a meeting activities report.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.