Meraki-Netzwerke prüfen und Microsoft Teams alarmieren

# Manualtrigger Workflow ## Overview Automated workflow: Manualtrigger Workflow. This workflow integrates 10 different services: stickyNote, httpRequest, code, scheduleTrigger, merge. It contains 29 nodes and follows best practices for error handling and security. ## Workflow Details - Total Nodes: 29 - Node Types: 10 - Error Handling: ✅ Implemented - Security: ✅ Hardened (no sensitive data) - Documentation: ✅ Complete ## Node Breakdown - When clicking "Execute Workflow": manualTrigger - Get Meraki Organizations: httpRequest - Get Network IDs: httpRequest - Get Org Name & ID: set - Combine latency to its respective Network: merge - Makes Latency and Loss Filterable: set - Filters Problematic sites: code - Average Latency & Loss over 5m: code - Get Uplink Loss and Latency: httpRequest - Schedule Trigger: scheduleTrigger - ... and 19 more nodes ## Usage Instructions 1. Configure Credentials: Set up all required API keys and credentials 2. Update Variables: Replace any placeholder values with actual data 3. Test Workflow: Run in test mode to verify functionality 4. Deploy: Activate the workflow for production use ## Security Notes - All sensitive data has been removed or replaced with placeholders - Error handling is implemented for reliability - Follow security best practices when configuring credentials ## Troubleshooting - Check error logs if workflow fails - Verify all credentials are properly configured - Ensure all required services are accessible