Keep an eye on network health and alert your team in minutes. This setup watches latency and packet loss across your sites and posts clear messages in Microsoft Teams when a threshold is crossed. It is designed for IT teams and service desks that need fast, noise free alerts during business hours.

A scheduler runs every five minutes on weekdays and can also be started by hand. The flow pulls your organizations, networks, and five minute uplink stats from the Meraki API. Set and Merge steps tie each network to its latency and loss data. Two short code steps average the last five readings and pass only sites above your limits. A Redis lookup blocks repeat alerts by checking if the site already has an active key. A Merge step keeps only non matches so Microsoft Teams receives new issues with the network name and a direct link to the site page. This cuts alert noise and helps techs act fast.

You will need a Meraki API key, a Microsoft Teams connection, and a Redis database. Adjust the latency and loss limits to match your SLA and edit the schedule to your support hours. Expect fewer manual checks, quicker triage, and a clean handoff to the team channel. This works well for MSPs, IT operations, and companies with many branches.

• Five minute weekday schedule with a manual test trigger for safe runs
• HTTP requests pull organizations, networks, and uplink loss and latency from the Meraki API
• Set nodes standardize fields like network ID, name, and a direct network URL
• Merge node enriches network records with their matching latency and loss stats
• Code step averages the last five readings to smooth spikes and reduce noise
• Code step filters only sites above the latency and loss thresholds
• Redis check prevents repeat alerts and stores a key with a 3 hour expiry
• Microsoft Teams message posts the site name and a clickable link for quick access

• Reduce manual network checks from 2 hours a day to under 5 minutes
• Cut duplicate alerts by about 90 percent using Redis with a 3 hour TTL
• Catch issues within 5 minutes to improve response time by 50 percent
• Connect Meraki and Microsoft Teams so alerts reach the right channel fast
• Scale to hundreds of networks across multiple organizations without extra work

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Cisco Meraki, Microsoft Teams and Redis. See the Tools Required section above for links to create accounts with these services.
3. In your Meraki dashboard, create an API key. In the n8n credentials manager, add a new HTTP Header Auth credential. Set Header Name to Authorization and Value to Bearer YOUR_API_KEY. Save the credential.
4. Open the Get Meraki Organizations node and choose the HTTP Header Auth credential you created. Ensure the Accept header is application/json in the node options.
5. Run the Get Meraki Organizations node once to confirm it returns your org list. Fix any 401 or 403 errors by checking the API key and Authorization header format.
6. Open the Message Techs node. In the credential dropdown, click Create new credential and follow the on screen steps to connect Microsoft Teams. Pick the team and channel for alerts.
7. Edit the Teams message text to include the network name and network URL field. Send a test message from the node to confirm channel access.
8. In the n8n credentials manager, create Redis credentials with your host, port, and password. Enable TLS if your provider requires it. Attach this credential to the Check if Alert Exists and Log the Alert nodes.
9. Open the Schedule Trigger and confirm the cron expression */5 8-16 * * 1-5 matches your support hours. Adjust if your time zone or hours are different.
10. Open the Filters Problematic sites code node and set your thresholds. The default is 300 ms latency and 2 percent loss. Save your changes.
11. Click Execute Workflow to test end to end. Verify that Average Latency and Loss over 5m outputs averages, that the Merge step keeps only new issues, and that a Teams message appears when a site crosses the limits.
12. Check your Redis database for a new key for the alerted network with a TTL close to 10800 seconds. If connection fails, verify host, port, password, and TLS settings, and allowlist n8n Cloud if needed.