> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/outbound-integrations/zoom/zoom-meeting-integration.md).

# Zoom Meeting Integration

Connect a Zoom account to ilert, and start a Zoom call on an incident with a conference bridge.

{% hint style="warning" %}
**Do not build new Zoom Meeting alert actions.** A meeting attached to a single alert is superseded by an incident [conference bridge](/incidents-and-status-pages/incidents/conference-bridges.md), which hangs off the incident alongside its channel, responders, and timeline. The Zoom Meeting type is marked deprecated in the connector catalogue and the alert action is being removed. Existing ones keep working until it is.
{% endhint %}

The Zoom Meeting connector authorizes ilert to create Zoom meetings in your Zoom account.

## Connect Zoom to ilert

{% hint style="info" %}
**Admin permission required**

Connecting a Zoom account needs the **Admin** or **Account owner** role in ilert.
{% endhint %}

{% stepper %}
{% step %}

## Open the connector catalogue

In the sidebar, go to **Settings** → **Connectors**. Find **Zoom Meeting** in the catalogue and click **Connect**.
{% endstep %}

{% step %}

## Name the connector

Choose **Zoom Meeting** as the type, give the connector a name, and save. ilert sends you to Zoom to authorize the app.
{% endstep %}

{% step %}

## Authorize ilert in Zoom

Agree to the requested permissions and click **Authorize**. Zoom returns you to ilert, where the connector is listed.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MVvPAJj6ASn-KnO5f4S%2F-MVvWrgMif6lAUBOACjB%2FScreenshot_16_03_21__15_53.png?alt=media&amp;token=ecc49303-7890-4fbe-aeb2-e3413027fa69" alt="Zoom&#x27;s consent screen, titled iLert is requesting access to your Zoom account, listing the chat channel, chatbot, and meeting permissions, with an Agree checkbox and an Authorize button."><figcaption><p>Zoom asks for the chat and meeting permissions together, because one ilert app covers both Zoom integrations.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Start a Zoom call on an incident

Open the incident and select **+ Start bridge** in the **Conference bridge** field, then use **Paste a link**: any Zoom meeting URL is attached as-is, and ilert labels the bridge as Zoom because it recognizes `zoom.us`. Everyone working the incident sees the same link, and responders paged after the bridge starts get a **Join call** link in their email.

Automatic provisioning — ilert creating the Zoom meeting for you — is available for Microsoft Teams only today. See [conference bridges](/incidents-and-status-pages/incidents/conference-bridges.md) for what a bridge carries and who can attach one.

## FAQ <a href="#faq" id="faq"></a>

### Can I link multiple Zoom accounts to an ilert account?

Yes.

### How do I uninstall the ilert app from my Zoom account?

1. Sign in to your Zoom account and go to the Zoom App Marketplace.
2. Click **Manage**, then **Installed Apps** — or search for the **iLert** app.
3. Open the **iLert** app.
4. Click **Uninstall**.

### I have a Zoom Meeting alert action already. What happens to it?

It keeps creating a meeting per alert for now. Move the habit to incidents: declare an incident for the problems worth a call, and attach a conference bridge there.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/integrations/outbound-integrations/zoom/zoom-meeting-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.