Component to help create automations for events that occur in your Zoom account.

{% if installed %}

Uninstall

If you choose to uninstall this integration, be sure to go to the installed apps list in your Zoom account and uninstall the app from there, otherwise it will continue to send events to your HA instance.

{% endif %}

Background

Zoom allows users to create custom applications that can trigger a JSON POST to a webhook when certain events in your Zoom account occur. This component will enable you to activate a custom Zoom app for your account which you can then use to subscribe to Zoom events.

Example: I am currently using this integration to subscribe to the User's presence status has been updated event which occurs every time I enter or exit a meeting. An event automation gets triggered on each status change and enables/disables a do not disturb signal for my wife.

Because the event name is included in the JSON payload sent to the webhook, you can subscribe to any events you would like within the same app and use automation conditions to conditionally do different things depending on the event.

Pre-Requisites

Your Home Assistant instance must be externally accessible from the Internet. The External URL will also need to be appropriately set and should replace <BASE_HA_URL> references in the installation instructions. You can do this in your configuration.yaml or through the UI as mentioned in the docs.

Home Assistant Cloud (Nabu Casa) Users

If you have a Home Assistant Cloud subscription, this integration will use your Nabu Casa cloud URL (e.g., https://<unique-id>.ui.nabu.casa) instead of your configured external URL. When setting up your Zoom app, use your Nabu Casa cloud URL for the Redirect URL for OAuth and Allow List entries, not your external URL.

Enterprise/Corporate Account Restrictions

If your Zoom account is managed by an organization (Enterprise or Corporate accounts), your administrator may restrict certain capabilities. This integration requires the ability to:

• Create custom OAuth apps in the Zoom Marketplace
• Access and configure webhooks for event subscriptions
• Request necessary OAuth scopes (e.g., chat_contact:read for presence status)

If your organization has disabled these permissions for users, this integration will not work. Contact your Zoom administrator to request access to app development features, or use a personal Zoom account instead.

Zoom Webhook Requirements

Zoom has specific requirements for webhook endpoints (see docs):

• HTTPS required: Your Home Assistant must be accessible via HTTPS with TLSv1.2+ and a valid certificate
• 3-second response deadline: Zoom expects a response within 3 seconds. If your HA instance is slow to respond, webhooks may fail
• 72-hour revalidation: Zoom automatically revalidates your endpoint every 72 hours
• Retry policy: Failed webhook deliveries are retried at 5 min, 20 min, and 60 min intervals. After 3 failures, no further webhooks for that event will be sent until revalidation succeeds

Troubleshooting: If your Home Assistant instance experiences downtime for more than 72 hours, or if you've just upgraded from a version that used verification_token to one that uses secret_token, you may need to disable and re-enable Event Subscriptions in your Zoom app's Features section to trigger revalidation.

Migrating from verification_token to secret_token

Zoom has deprecated verification tokens in favor of secret tokens with HMAC signature validation. If you're upgrading from an older version of this integration:

1. Get your Secret Token from your Zoom app under Features > Access
2. If using configuration.yaml: Manually replace verification_token with secret_token in your config file and restart Home Assistant
3. If using UI-only setup: The integration will prompt you to enter your secret token during reauth
4. After updating, you may need to disable and re-enable Event Subscriptions in Zoom to trigger revalidation

Installation (Single AccounzRMonitoring)

NOTE: If you want to monitor multiple Zoom accounts, skip to the next set of installation instructions

Entities Provided

Binary Sensor

	Description
Name	binary_sensor.zoom_{PROVIDED_ACCOUNT_NAME}
Purpose	Tracks user presence on a Zoom call by consuming the User's presence status has been updated event. If the state is on, the user is on a Zoom call.
Notes	If User's presence status has been updated is not enabled in the Zoom App's Event Subscriptions, this sensor will not work and can be disabled.

Event Entities (Diagnostic)

Event entities are created dynamically when the integration receives a new webhook event type for the first time. These entities provide a way to track and automate based on any Zoom webhook event.

	Description
Name	event.{PROVIDED_ACCOUNT_NAME}_{event_type} (e.g., event.zoom_presence_status_updated)
Purpose	Tracks individual Zoom webhook event types. Each unique event type gets its own entity.
Attributes	event_ts (timestamp), payload (full event payload), last_event_ts, last_payload (from previous event)
Use Cases	Automations: Trigger actions when specific Zoom events occur (meeting started, recording available, etc.). Troubleshooting: View the last received payload for debugging webhook issues. History: Track when events occurred via entity history.

Pre-created entities (disabled by default):

• endpoint.url_validation - Zoom's periodic endpoint revalidation (every 72 hours)
• user.presence_status_updated - Presence status changes (redundant with the binary sensor)

These entities can be enabled in the entity registry if needed for automation or debugging.

Example: If you subscribe to meeting.started events in your Zoom app, an event.zoom_meeting_started entity will be created the first time that event is received.

Installation Instructions

Set up your Zoom app

1. Go to the Build App page.
2. Click on Create in the OAuth card.
3. Enter an application name of your choice, select User-managed app, deselect Would you like to publish this app on Zoom App Marketplace?, and then click on Create.
4. Copy your Client ID and Client Secret somewhere as you will need them later to configure Home Assistant.
5. Enter the following Redirect URL for OAuth: <BASE_HA_URL>/auth/external/callback (replace <BASE_HA_URL> with your Nabu Casa cloud URL if you have Home Assistant Cloud, otherwise use your configured external URL, e.g. https://ha.example.com)
6. Enter your <BASE_HA_URL> in the Add Allow List section (use the same URL as step 5), then hit Continue.
7. The App Name should already be filled out. A Short Description and Long Description are required, but since this app is only for you, it doesn't matter what you enter here. You will also need to add a Name and Email Address in the Developer Contact Information section. Click Continue once you are done.
8. Enable Event Subscriptions and click on Add new event subscriptions.
9. Enter a name for this subscription (does not matter).
10. Your Event notification endpoint URL should be set to <BASE_HA_URL>/api/zoom.
11. Now click on Add events. From this menu, you can choose what events you want to subscribe to. To use the binary_sensor provided by the integration, you would go to the User Activity event type and check the box next to User's presence status has been updated. If you want to get more details about when you start a meeting, add Start Meeting under Meeting.
12. Make note of the Secret Token found under Features > Access as you will need it for your configuration later.
13. Once you are done, click Done, then Save the subscription before hitting Continue.
14. The Scopes section should have already be updated to include at least one permission based on the events you choose to monitor. If you want to use the binary_sensor, you will need to add another scope so that the initial status of your sensor is set correctly, otherwise the integration will naively restore your last state on restart. To do this, click Add Scopes in the top right of the main page, go to the Team Chat section, enable the checkbox next to View current user's team chat contact information (the scope is called chat_contact:read) and click Done. Click Continue to save what you did.
15. You are now ready to configure Home Assistant!

Install the Zoom integration via HACS

If you don't already have HACS installed, follow the instructions here. Once HACS has been installed, go the HACS menu in your sidebar menu, go to Integrations, and click Add. Search for Zoom and select INSTALL THIS REPOSITORY IN HACS. You may need to restart your Home Assistant instance in order for it to be able to see the new integration. You may also need to hard refresh the UI in order to see the Integration in the main Integrations menu.

Configure HomeAssistant

You can either do the initial setup through the UI or in your configuration.yaml file. Both methods are described below.

Using the UI

1. Click Install
2. In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Zoom". Select it.
3. You will be asked to provide the Client ID and Client Secret that Zoom gave you earlier as well as the Secret Token you grabbed from Zoom in the earlier section. Enter them in and click Submit.
4. Skip to "Finish Setup" section below

Using configuration.yaml

1. Click Install
2. Create a new top level configuration item in configuration.yaml as follows (you may need to restart your HA instance to pick up the changes once they are added):

zoom:
    client_id: <CLIENT_ID_FROM_YOUR_CUSTOM_ZOOM_APP>
    client_secret: <CLIENT_SECRET_FROM_YOUR_CUSTOM_ZOOM_APP>
    secret_token: <SECRET_TOKEN_FROM_FEATURES_ACCESS_IN_YOUR_CUSTOM_ZOOM_APP>

3. In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Zoom". Select it.
4. Skip to "Finish Setup" section below

Finish setup

5. Enter a name for the account you plan to connect to Zoom. This will be useful if you plan to monitor more than one Zoom account.
6. If you are not already logged into Zoom, you will be asked to log in.
7. Authorize the app for the Scopes that were configured earlier.
8. Start automating!

NOTE: Once your app is configured and activated, you can go back to Zoom at any time to update the events you are subscribed to. To do this, go to your Created Apps list and click on the app name. Go to the Feature section and expand Event Subscriptions, then edit your existing subscription and update it. Once you are done, you should check the Scopes section to make sure the permissions make sense for the events you selected. In my testing Zoom does a good job of updating this based on the scopes you select. Once you are done with that, you should remove the integration from the Integrations menu in the HA UI and re-add it. You may need to reauthorize the application if the scopes required have changed.

Installation (Multiple Account Monitoring)

Entities Provided

Binary Sensor

	Description
Name	binary_sensor.zoom_{PROVIDED_ACCOUNT_NAME}
Purpose	Tracks user presence on a Zoom call by consuming the User's presence status has been updated event. If the state is on, the user is on a Zoom call.
Notes	If User's presence status has been updated is not enabled in the Zoom App's Event Subscriptions, this sensor will not work and can be disabled.

Event Entities (Diagnostic)

Event entities are created dynamically when the integration receives a new webhook event type for the first time. These entities provide a way to track and automate based on any Zoom webhook event.

	Description
Name	event.{PROVIDED_ACCOUNT_NAME}_{event_type} (e.g., event.zoom_presence_status_updated)
Purpose	Tracks individual Zoom webhook event types. Each unique event type gets its own entity.
Attributes	event_ts (timestamp), payload (full event payload), last_event_ts, last_payload (from previous event)
Use Cases	Automations: Trigger actions when specific Zoom events occur (meeting started, recording available, etc.). Troubleshooting: View the last received payload for debugging webhook issues. History: Track when events occurred via entity history.

Pre-created entities (disabled by default):

• endpoint.url_validation - Zoom's periodic endpoint revalidation (every 72 hours)
• user.presence_status_updated - Presence status changes (redundant with the binary sensor)

These entities can be enabled in the entity registry if needed for automation or debugging.

Example: If you subscribe to meeting.started events in your Zoom app, an event.zoom_meeting_started entity will be created the first time that event is received.

Installation Instructions

Set up your Zoom app (do this for each account you want to monitor)

1. Go to the Build App page.
2. Click on Create in the OAuth card.
3. Enter an application name of your choice, select User-managed app, deselect Would you like to publish this app on Zoom App Marketplace?, and then click on Create.
4. Copy your Client ID and Client Secret somewhere as you will need them later to configure Home Assistant.
5. Enter the following Redirect URL for OAuth: <BASE_HA_URL>/auth/external/callback (replace <BASE_HA_URL> with your Nabu Casa cloud URL if you have Home Assistant Cloud, otherwise use your configured external URL, e.g. https://ha.example.com)
6. Enter your <BASE_HA_URL> in the Whitelist URL section (use the same URL as step 5), then hit Continue.
7. The App Name should already be filled out. A Short Description and Long Description are required, but since this app is only for you, it doesn't matter what you enter here. You will also need to add a Name and Email Address in the Developer Contact Information section. Click Continue once you are done.
8. Make note of the Secret Token found under Features > Access as you will need it for your configuration later.
9. Enable Event Subscriptions and click on Add new event subscriptions.
10. Enter a name for this subscription (does not matter).
11. Your Event notification endpoint URL should be set to <BASE_HA_URL>/api/zoom.
12. Now click on Add events. From this menu, you can choose what events you want to subscribe to. To use the binary_sensor provided by the integration, you would go to the User Activity event type and check the box next to User's presence status has been updated. If you want to get more details about when you start a meeting, add Start Meeting under Meeting.
13. Once you are done, click Done, then Save the subscription before hitting Continue.
14. The Scopes section should have already be updated to include at least one permission based on the events you choose to monitor. If you want to use the binary_sensor, you will need to add another scope so that the initial status of your sensor is set correctly, otherwise the integration will naively restore your last state on restart. To do this, click Add Scopes in the top right of the main page, go to the Chat section, enable the checkbox next to View current user's chat contact information (the scope is called chat_contact:read) and click Done. Click Continue to save what you did.
15. You are now ready to configure Home Assistant!

Install the Zoom integration via HACS

If you don't already have HACS installed, follow the instructions here. Once HACS has been installed, go the HACS menu in your sidebar menu, go to Integrations, and click Add. Search for Zoom and select INSTALL THIS REPOSITORY IN HACS. You may need to restart your Home Assistant instance in order for it to be able to see the new integration. You may also need to hard refresh the UI in order to see the Integration in the main Integrations menu.

Configure HomeAssistant

You can either do the initial setup through the UI or in your configuration.yaml file. Both methods are described below.

1. Click Install
2. Create a new top level configuration item in configuration.yaml as follows (you will need to restart your HA instance to pick up the changes once they are added):

zoom:
  - client_id: <ACCOUNT1_CLIENT_ID_FROM_YOUR_CUSTOM_ZOOM_APP>
    client_secret: <ACCOUNT1_CLIENT_SECRET_FROM_YOUR_CUSTOM_ZOOM_APP>
    secret_token: <ACCOUNT1_SECRET_TOKEN_FROM_FEATURES_ACCESS>
    name: ACCOUNT1 (make sure you use a name that will make it easy for you to know which Zoom account to log into later)
  - client_id: <ACCOUNT2_CLIENT_ID_FROM_YOUR_CUSTOM_ZOOM_APP>
    client_secret: <ACCOUNT2_CLIENT_SECRET_FROM_YOUR_CUSTOM_ZOOM_APP>
    secret_token: <ACCOUNT2_SECRET_TOKEN_FROM_FEATURES_ACCESS>
    name: ACCOUNT2 (make sure you use a name that will make it easy for you to know which Zoom account to log into later)

3. In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Zoom". Select it.
4. Select the name for the account you want to link to.
5. If you are not already logged into Zoom, you will be asked to log in. You must log into the account that the Zoom app that uses the credentials from step 4 is created in.
6. Authorize the app for the Scopes that were configured earlier.
7. Start automating!

NOTE: Once your app is configured and activated, you can go back to Zoom at any time to update the events you are subscribed to. To do this, go to your Created Apps list and click on the app name. Go to the Feature section and expand Event Subscriptions, then edit your existing subscription and update it. Once you are done, you should check the Scopes section to make sure the permissions make sense for the events you selected. In my testing Zoom does a good job of updating this based on the scopes you select. Once you are done with that, you should remove the integration from the Integrations menu in the HA UI and re-add it. You may need to reauthorize the application if the scopes required have changed.

Change Zoom status to binary sensor state mapping

By default, the binary sensor will be on, or Connected, when your Zoom account is in the following statuses:

• In_Meeting
• Presenting
• On_Phone_Call

All other statuses will cause the binary sensor to be off, or Disconnected. If you'd like to change this behavior, you can update which statuses are used to determine when the binary sensor is on by using the Options config flow as follows:

1. Navigate to "Configuration" -> "Integrations" and look for the Zoom card
2. Click the "Options" link on the card
3. Select your statuses
4. Click "Submit" to apply the changes

Monitoring custom events (non-presence related)

Events from all of the linked accounts will all be sent using the same event, so in order to create sensible automations, you will need to be able to distinguish between accounts. The binary_sensor created for each account you link to will have all of the profile information you need. You can use the id, email, or account_id attributes of the sensor to identify events coming from the account. The information you need from the webhook event to match to the correct account will be in different places depending on the event type. In addition, you should lowercase both the property from the event and the sensor data to ensure a match. In testing I found that Zoom sends a lowercase id, so it just seems like the safer approach.

Example

For the user.presence_status_updated event, a user_id is provided by trigger.event.data.payload.object.id. I can match that to the id of the entry for Hello Worlds as follows :

condition:
  - {{ trigger.event.data.payload.object.id.lower() == state_attr('binary_sensor.zoom_hello_world', 'id').lower() }}

Creating Automations

You are free to create automations however you see fit, but here are some tips:

Using Event Entities (Recommended)

Event entities provide a cleaner way to trigger automations. Once an event entity exists (created automatically on first webhook), you can use it directly:

trigger:
  - platform: state
    entity_id: event.zoom_presence_status_updated
action:
  - service: notify.mobile_app
    data:
      message: "Zoom status changed to {{ trigger.to_state.attributes.payload.object.presence_status }}"

You can also access the previous event's data using last_payload and last_event_ts attributes for comparison logic.

Using Raw Webhook Events

Alternatively, you can trigger on the raw zoom_webhook event:

trigger:
  platform: event
  event_type: zoom_webhook
  event_data:
    event: <ZOOM_EVENT_NAME>

Conditions and Actions

To see the schema of various events, check Zoom's Webhook Reference docs. On the left hand side navigation, you can click into the various Event types and see the format of the JSON that will be sent to HA.

To create a condition on an event type, use something like the following:

condition:
  condition: "{{ trigger.event.data.event == "user.presence_status_updated" }}"

You will likely want to act on information in trigger.event.data.payload.object, either in a condition or an action. Be sure to use value_template and data_template when accessing this information in your configured automation if HA version is below 0.115.0.

You can use some input_texts with an automation too, like this:

Expand

- alias: Zoom status updates
  description: ''
  trigger:
  - platform: event
    event_type: zoom_webhook
  condition: []
  action:
  - choose:
    - conditions: "{{ trigger.event.data.event == "user.presence_status_updated" }}"
      sequence:
      - data:
          entity_id: input_text.zoom_status
          value: '{{ trigger.event.data.payload.object.presence_status }}'
        service: input_text.set_value
    - conditions: "{{ trigger.event.data.event == "meeting.started" }}"
      sequence:
      - data:
          entity_id: input_text.zoom_meeting
          value: '{{ trigger.event.data.payload.object.topic }}'
        service: input_text.set_value
  mode: single

---