> 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/inbound-integrations/cisco-meraki.md).
# Cisco Meraki Integration
Send Cisco Meraki network events into ilert and notify your team via SMS, phone call, push, and other channels to improve your infrastructure reliability.
[The Cisco Meraki](https://meraki.cisco.com/) integration turns wireless, switching, and security appliance events into structured alerts within ilert. This ensures near-instant visibility on network issues, enforceable escalation paths, and consolidated incident reports, boosting reliability and reducing downtime.
## In ilert: Create a Cisco Meraki alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Cisco Meraki**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In Cisco Meraki: Add ilert as a webhook receiver
1. Select the desired **Network**
2. In the sidebar, go to **Alerts & AI** -> **Destinations** -> **Webhook**
3. On the next page, scroll down to **Webhooks** and enter a **Name**, the Webhook URL generated in ilert and choose **Meraki (included)** as payload template
4. Click on **Send test webhook**, to send a test alert to ilert
5. Click on **Save** to save the webhook
## FAQ
#### **Will alerts in ilert be resolved automatically?**
Yes, however, only certain alert type IDs will automatically resolve the corresponding alerts in ilert. These types include:
* cellular\_up
* sensor\_water\_cable\_reconnected
* sensor\_probe\_cable\_reconnected
* sensor\_battery\_improved
* port\_connected
* power\_supply\_up
* reconnected
* started\_reporting
* pcc\_outage\_end
* bluetooth\_in
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/integrations/inbound-integrations/cisco-meraki.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
