Meraki パケットロスと遅延アラートを Microsoft Teams に
上級
これはIT Ops, SecOps分野の自動化ワークフローで、23個のノードを含みます。主にSet, Code, Merge, Redis, HttpRequestなどのノードを使用。 Merakiのパケットロスと遅延アラートをMicrosoft Teamsにプッシュ
前提条件
- •Redisサーバー接続情報
- •ターゲットAPIの認証情報が必要な場合あり
ワークフロープレビュー
ノード接続関係を可視化、ズームとパンをサポート
ワークフローをエクスポート
以下のJSON設定をn8nにインポートして、このワークフローを使用できます
{
"meta": {
"instanceId": "257476b1ef58bf3cb6a46e65fac7ee34a53a5e1a8492d5c6e4da5f87c9b82833",
"templateId": "2054"
},
"nodes": [
{
"id": "3b18d784-eded-4b74-ac44-b25565049e13",
"name": "「ワークフローを実行」クリック時",
"type": "n8n-nodes-base.manualTrigger",
"position": [
380,
400
],
"parameters": {},
"typeVersion": 1
},
{
"id": "96eadd32-17c2-44b0-a00b-8e2ddcecaafa",
"name": "Meraki組織の取得",
"type": "n8n-nodes-base.httpRequest",
"notes": "This node uses an API call to Meraki using the URL https://api.meraki.com/api/v1/organizations\n\nthe Authorization header is what is used to authenticate. You also have to set it to accept json",
"position": [
620,
320
],
"parameters": {
"url": "https://api.meraki.com/api/v1/organizations",
"options": {
"redirect": {
"redirect": {}
}
},
"sendHeaders": true,
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"headerParameters": {
"parameters": [
{
"name": "Accept",
"value": "application/json"
}
]
}
},
"credentials": {
"httpHeaderAuth": {
"id": "12",
"name": "Header Auth account"
}
},
"typeVersion": 4.1
},
{
"id": "444071ea-a364-45a6-9430-0338d2752b18",
"name": "ネットワークIDの取得",
"type": "n8n-nodes-base.httpRequest",
"notes": "This node uses a URL with an expression in the middle to do an API call for each ORG ID that was pulled to pull all the network's for each org",
"position": [
1020,
240
],
"parameters": {
"url": "=https://api.meraki.com/api/v1/organizations/{{ $json.OrgID }}/networks ",
"options": {
"redirect": {
"redirect": {}
}
},
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "Authorization"
},
{
"name": "Accept",
"value": "application/json"
}
]
}
},
"typeVersion": 4.1
},
{
"id": "42deea02-e2d2-4ba6-97f7-698c219715a5",
"name": "組織名とIDの取得",
"type": "n8n-nodes-base.set",
"notes": "This takes the output data from the previous node and changes the variables to better suit what we'll be using. ",
"position": [
840,
240
],
"parameters": {
"fields": {
"values": [
{
"name": "CompanyName",
"stringValue": "={{ $json.name }}"
},
{
"name": "OrgID",
"stringValue": "={{ $json.id }}"
}
]
},
"include": "selected",
"options": {}
},
"typeVersion": 3.2
},
{
"id": "3d5ce6a8-bf05-4457-88e6-c5ad5a995b1d",
"name": "遅延を対応するネットワークに結合",
"type": "n8n-nodes-base.merge",
"notes": "This node matches on the NetworkID field, so that the networks we pulled earlier and the Loss / Latency can be combined into one dataset",
"position": [
1500,
400
],
"parameters": {
"mode": "combine",
"options": {},
"joinMode": "enrichInput1",
"mergeByFields": {
"values": [
{
"field1": "NetworkID",
"field2": "networkId"
}
]
}
},
"notesInFlow": false,
"typeVersion": 2.1
},
{
"id": "caafd6dd-a2b2-405d-a078-cea3bb615788",
"name": "遅延と損失をフィルタリング可能に設定",
"type": "n8n-nodes-base.set",
"notes": "Like before, This takes the output data from the previous node and changes the variables to better suit what we'll be using. ",
"position": [
1680,
400
],
"parameters": {
"fields": {
"values": [
{
"name": "networkId",
"stringValue": "={{ $json.networkId }}"
},
{
"name": "NetworkName",
"stringValue": "={{ $json.NetworkName }}"
},
{
"name": "networkURL",
"stringValue": "={{ $json.networkURL }}"
},
{
"name": "Serial",
"stringValue": "={{ $json.serial }}"
},
{
"name": "TS0-Loss",
"stringValue": "={{ $json.timeSeries[0].lossPercent }}"
},
{
"name": "TS1-Loss",
"stringValue": "={{ $json.timeSeries[1].lossPercent }}"
},
{
"name": "TS2-Loss",
"stringValue": "={{ $json.timeSeries[2].lossPercent }}"
},
{
"name": "TS3-Loss",
"stringValue": "={{ $json.timeSeries[3].lossPercent }}"
},
{
"name": "TS4-Loss",
"stringValue": "={{ $json.timeSeries[4].lossPercent }}"
},
{
"name": "TS0-Latency",
"stringValue": "={{ $json.timeSeries[0].latencyMs }}"
},
{
"name": "TS1-Latency",
"stringValue": "={{ $json.timeSeries[1].latencyMs }}"
},
{
"name": "TS2-Latency",
"stringValue": "={{ $json.timeSeries[2].latencyMs }}"
},
{
"name": "TS3-Latency",
"stringValue": "={{ $json.timeSeries[3].latencyMs }}"
},
{
"name": "TS4-Latency",
"stringValue": "={{ $json.timeSeries[4].latencyMs }}"
}
]
},
"include": "selected",
"options": {}
},
"typeVersion": 3.2
},
{
"id": "c695fd89-c884-4794-b0e5-51b91a71ac5c",
"name": "問題のあるサイトをフィルタリング",
"type": "n8n-nodes-base.code",
"notes": "This node uses JavaScript to look at the calculated averages and if they pass the threshold for 300ms Latency or 2% Loss it will pass that site info forward",
"position": [
2040,
400
],
"parameters": {
"jsCode": "// Function to filter items based on averageLatency and averageLoss\nfunction filterItems(items) {\n return items.filter(item =>\n item.AverageLatency >300 || item.AverageLoss > 2\n );\n}\n\n// Get the input items from the previous node\nconst inputItems = items.map(item => item.json); // Adjust based on your actual data structure\n\n// Filter the items based on the conditions\nconst filteredItems = filterItems(inputItems);\n\n// Return the filtered items to the workflow\nreturn filteredItems.map(item => {\n return { json: item }; // Format each filtered item as JSON\n});\n"
},
"typeVersion": 2
},
{
"id": "6db219fd-f54d-4bf8-b150-9c4f3069cf92",
"name": "5分間の平均遅延と損失",
"type": "n8n-nodes-base.code",
"notes": "This node uses JavaScript to calculate the average over the last 5 entries of packet loss and latency",
"position": [
1860,
400
],
"parameters": {
"jsCode": "// Assuming $input.all() is an array of items and each item has a json property\nfunction calculateAverages(inputItems) {\n return inputItems.map(item => {\n // Calculate total and average loss\n const totalLoss = \n parseFloat(item.json['TS0-Loss']) +\n parseFloat(item.json['TS1-Loss']) +\n parseFloat(item.json['TS2-Loss']) +\n parseFloat(item.json['TS3-Loss']) +\n parseFloat(item.json['TS4-Loss']);\n const averageLoss = totalLoss / 5;\n item.json['AverageLoss'] = averageLoss;\n\n // Calculate total and average latency\n const totalLatency = \n parseFloat(item.json['TS0-Latency']) +\n parseFloat(item.json['TS1-Latency']) +\n parseFloat(item.json['TS2-Latency']) +\n parseFloat(item.json['TS3-Latency']) +\n parseFloat(item.json['TS4-Latency']);\n const averageLatency = totalLatency / 5;\n item.json['AverageLatency'] = averageLatency;\n\n // Return the modified item\n return item;\n });\n}\n\nreturn calculateAverages($input.all());\n"
},
"typeVersion": 2
},
{
"id": "f3831843-2596-492d-b800-7d349e443293",
"name": "アップリンク損失と遅延の取得",
"type": "n8n-nodes-base.httpRequest",
"notes": "This uses a URL with an expression in the middle so that for each org ID it will pull the Loss and Latency for their uplinks. ",
"position": [
840,
400
],
"parameters": {
"url": "=https://api.meraki.com/api/v1/organizations/{{ $json.id }}/devices/uplinksLossAndLatency?timespan=300",
"options": {
"redirect": {
"redirect": {}
}
},
"sendHeaders": true,
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"headerParameters": {
"parameters": [
{
"name": "Accept",
"value": "application/json"
}
]
}
},
"credentials": {
"httpHeaderAuth": {
"id": "12",
"name": "Header Auth account"
}
},
"typeVersion": 4.1
},
{
"id": "87c3f32c-de4f-48fd-a711-3521a008c245",
"name": "スケジュールトリガー",
"type": "n8n-nodes-base.scheduleTrigger",
"notes": "schedules the workflow to run every 5 minutes mon-fri 8am-5pm",
"position": [
380,
240
],
"parameters": {
"rule": {
"interval": [
{
"field": "cronExpression",
"expression": "*/5 8-16 * * 1-5"
}
]
}
},
"typeVersion": 1.1
},
{
"id": "572adb5c-6745-4b4e-89d8-a97835c3d486",
"name": "ネットワーク変数の設定",
"type": "n8n-nodes-base.set",
"notes": "Like before, This takes the output data from the previous node and changes the variables to better suit what we'll be using. ",
"position": [
1220,
240
],
"parameters": {
"fields": {
"values": [
{
"name": "NetworkID",
"stringValue": "={{ $json.id }}"
},
{
"name": "NetworkName",
"stringValue": "={{ $json.name }}"
},
{
"name": "networkURL",
"stringValue": "={{ $json.url }}"
}
]
},
"include": "selected",
"options": {}
},
"typeVersion": 3.2
},
{
"id": "01717ed3-1012-4eda-9da9-567038132e06",
"name": "マージ",
"type": "n8n-nodes-base.merge",
"notes": "This looks at the problematic sites as well as the info from the database. It will pass on all non-matching as if the site name matches with the database then that means we have an open alert for that site already.",
"position": [
2720,
300
],
"parameters": {
"mode": "combine",
"options": {},
"joinMode": "keepNonMatches",
"mergeByFields": {
"values": [
{
"field1": "NetworkName",
"field2": "NetworkName"
}
]
},
"outputDataFrom": "input2"
},
"typeVersion": 2.1
},
{
"id": "a20f6f7c-0c92-4db9-903b-e322d67b536d",
"name": "アラート存在確認",
"type": "n8n-nodes-base.redis",
"notes": "This node Looks to see if the alert already exists in the Redis database. If it does exist it won't alert us in Teams",
"position": [
2300,
240
],
"parameters": {
"key": "={{ $json.NetworkName }}",
"options": {
"dotNotation": "={{ true }}"
},
"operation": "get",
"propertyName": "NetworkName"
},
"typeVersion": 1,
"alwaysOutputData": true
},
{
"id": "63590446-2938-443a-adbe-bfc0ba89008c",
"name": "レスポンス作成",
"type": "n8n-nodes-base.code",
"notes": "If the alert isn't in the database all the Redis will respond with is \"null\" \n\nother n8n nodes see null as (no data) and show blank which is fair. So I made this node to look at the null responses and make a response of \"false\" for a \"alertExists\" variable. that way we have something to filter on",
"position": [
2500,
240
],
"parameters": {
"jsCode": "return items.map(item => {\n // Check if the 'NetworkName' property is not null, indicating an alert exists.\n // If 'NetworkName' is null, no alert exists for this network.\n const alertExists = item.json.NetworkName !== null;\n\n // Set the alertExists property correctly based on the condition.\n item.json.alertExists = alertExists;\n\n return item;\n});\n"
},
"typeVersion": 2
},
{
"id": "c63e2a45-bf5e-455f-8012-9868d55aa3e2",
"name": "技術担当者へのメッセージ",
"type": "n8n-nodes-base.microsoftTeams",
"notes": "sends an alert to Dispatch with info related to the site.",
"position": [
2920,
300
],
"parameters": {
"chatId": "19:bfd41d9621e544c88ae9f2f275e373b5@thread.v2",
"message": "=<strong>Loss & Latency Alert</strong> <br><br>\n<strong>Network Name:</strong> <a href=\"{{ $json.networkURL }}\">{{ $json.NetworkName }}</a> <br>\n<strong>Average Loss:</strong> {{ $json.AverageLoss }}% <br>\n<strong>Average Latency:</strong> {{ $json.AverageLatency }} <br> ",
"options": {},
"resource": "chatMessage"
},
"typeVersion": 1.1
},
{
"id": "b4ae54cd-8345-4611-9fbe-32e7537855a9",
"name": "アラートのログ記録",
"type": "n8n-nodes-base.redis",
"notes": "Logs the alert and sets the TTL to 3h, after 3h Redis will delete the entry and if the site is still having issues, the next run of the workflow will notify us again",
"position": [
3120,
300
],
"parameters": {
"key": "={{ $('Merge').item.json.NetworkName }}",
"ttl": 10800,
"value": "={{ $('Merge').item.json.NetworkName }}",
"expire": true,
"keyType": "string",
"operation": "set"
},
"typeVersion": 1,
"alwaysOutputData": true
},
{
"id": "05416de5-a0c0-4ff8-bfc5-3d26f0d88139",
"name": "付箋",
"type": "n8n-nodes-base.stickyNote",
"position": [
573.394087003982,
143.69977924944794
],
"parameters": {
"width": 791.5865288559442,
"height": 462.84878343542437,
"content": "## Pulling in Info \nThis section pulls in all the data we will need to see any possible errors and generate our alert\n"
},
"typeVersion": 1
},
{
"id": "aeb1c8a6-3cec-4899-83e2-098d0b1a9703",
"name": "付箋1",
"type": "n8n-nodes-base.stickyNote",
"position": [
1464,
211
],
"parameters": {
"width": 688.5000872281419,
"height": 411.1258278145692,
"content": "## Changing data\nThis section pulls together the data we got from the first section and sets everything up to be notified "
},
"typeVersion": 1
},
{
"id": "9ca9e89b-61ce-4b3f-af8e-bf03daff6710",
"name": "付箋2",
"type": "n8n-nodes-base.stickyNote",
"position": [
2260,
60
],
"parameters": {
"width": 1015.6997792494475,
"height": 614.8167770419421,
"content": "## Notify\nThis last section is for the push of the alert as well as storing the alert as to not re-notify every time the workflow runs"
},
"typeVersion": 1
},
{
"id": "801879be-e83b-4c74-b8ac-b20157ca32d1",
"name": "付箋3",
"type": "n8n-nodes-base.stickyNote",
"position": [
600,
640
],
"parameters": {
"width": 673.6064168725538,
"height": 394.26386951839356,
"content": "## Explanation\nusing an HTTP request you will can do a get request for all Organizations your Meraki account has access to. \n\nYou will have to Generate your own API key inside of the Meraki Dashboard explained here https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API\n\nYou will have to add two headers to your HTTPS node Authorization and Accept. the 1st is how you'll authenticate with Meraki and the second is how it will know how to answer the request. \n\nUsing the same methods you'll do a get for Organizations, Network IDs and Uplink stats\n\nUsing the Set nodes to organize the data in a \"neat\" way"
},
"typeVersion": 1
},
{
"id": "2b028326-0776-4b9b-bdf2-d79949809092",
"name": "付箋4",
"type": "n8n-nodes-base.stickyNote",
"position": [
1480,
660
],
"parameters": {
"width": 645.9603701592033,
"height": 389.89870424786454,
"content": "## Explanation\nthe Merge node will combine the Networks with their respective stats by matching on NetworkID and networkid and enriching the input \n\nagain we add a set node to better organize the statistics of the uplinks. \n\nThe first JS node will average the 5 Time stamps of Latency and Packet loss \n\nThe last JS node will send the data forward only for sites that pass the threshold (in this example 300ms latency and 2% packet loss) "
},
"typeVersion": 1
},
{
"id": "f7c1448d-3a03-4196-bde6-a1aea92f28ad",
"name": "付箋5",
"type": "n8n-nodes-base.stickyNote",
"position": [
2300,
700
],
"parameters": {
"width": 913.6905067516504,
"height": 523.763772544089,
"content": "## Explanation \nwe will send the problematic sites to both the Redis node and the Merge node. \n\nThe Redis node does a get request to see if a key exists matching the Network name in Meraki. If so it will respond with the Network name, If not it will respond with \"null\" \n\nthe n8n nodes view \"null\" as no data (which isn't exactly wrong as it literally is no data) but the next node will just say the input is blank so I've added the JS node to look at the output and respond if an alert does or doesn't exist based on the response of the Redis node. \n\nThis time we Merge looking at the NetworkName and keep all non-matching. The reason for this is because if they match, that means the key in the database exists, meaning we've already sent a message that the site is having issues. \n\nWe send the tickets forth that don't match and we will send a teams message that will notify of a Network passing the threshold for issues. I've included the Network URL and re-written the message to include a hyperlink that way the alert can be used to take you straight to the problematic site. \n\nFinally we log the site in the database with a TTL of 3h, this way if the error has not been fixed in 3h we will get another message. \n"
},
"typeVersion": 1
},
{
"id": "4f4d40ef-8e7d-420a-8273-4cfefd3af6e9",
"name": "付箋6",
"type": "n8n-nodes-base.stickyNote",
"position": [
1460,
-320
],
"parameters": {
"width": 670.6963066922013,
"height": 366.61782280504275,
"content": "## other usecases \n If you feel confident enough the Teams nodes can be replaced with a node that can generate a ticket for your PSA such as ConnectWise Mange. That way these are generating tickets rather than just messages. "
},
"typeVersion": 1
}
],
"pinData": {},
"connections": {
"01717ed3-1012-4eda-9da9-567038132e06": {
"main": [
[
{
"node": "c63e2a45-bf5e-455f-8012-9868d55aa3e2",
"type": "main",
"index": 0
}
]
]
},
"c63e2a45-bf5e-455f-8012-9868d55aa3e2": {
"main": [
[
{
"node": "b4ae54cd-8345-4611-9fbe-32e7537855a9",
"type": "main",
"index": 0
}
]
]
},
"63590446-2938-443a-adbe-bfc0ba89008c": {
"main": [
[
{
"node": "01717ed3-1012-4eda-9da9-567038132e06",
"type": "main",
"index": 0
}
]
]
},
"444071ea-a364-45a6-9430-0338d2752b18": {
"main": [
[
{
"node": "572adb5c-6745-4b4e-89d8-a97835c3d486",
"type": "main",
"index": 0
}
]
]
},
"87c3f32c-de4f-48fd-a711-3521a008c245": {
"main": [
[
{
"node": "96eadd32-17c2-44b0-a00b-8e2ddcecaafa",
"type": "main",
"index": 0
}
]
]
},
"42deea02-e2d2-4ba6-97f7-698c219715a5": {
"main": [
[
{
"node": "444071ea-a364-45a6-9430-0338d2752b18",
"type": "main",
"index": 0
}
]
]
},
"a20f6f7c-0c92-4db9-903b-e322d67b536d": {
"main": [
[
{
"node": "63590446-2938-443a-adbe-bfc0ba89008c",
"type": "main",
"index": 0
}
]
]
},
"572adb5c-6745-4b4e-89d8-a97835c3d486": {
"main": [
[
{
"node": "3d5ce6a8-bf05-4457-88e6-c5ad5a995b1d",
"type": "main",
"index": 0
}
]
]
},
"96eadd32-17c2-44b0-a00b-8e2ddcecaafa": {
"main": [
[
{
"node": "42deea02-e2d2-4ba6-97f7-698c219715a5",
"type": "main",
"index": 0
},
{
"node": "f3831843-2596-492d-b800-7d349e443293",
"type": "main",
"index": 0
}
]
]
},
"c695fd89-c884-4794-b0e5-51b91a71ac5c": {
"main": [
[
{
"node": "a20f6f7c-0c92-4db9-903b-e322d67b536d",
"type": "main",
"index": 0
},
{
"node": "01717ed3-1012-4eda-9da9-567038132e06",
"type": "main",
"index": 1
}
]
]
},
"f3831843-2596-492d-b800-7d349e443293": {
"main": [
[
{
"node": "3d5ce6a8-bf05-4457-88e6-c5ad5a995b1d",
"type": "main",
"index": 1
}
]
]
},
"6db219fd-f54d-4bf8-b150-9c4f3069cf92": {
"main": [
[
{
"node": "c695fd89-c884-4794-b0e5-51b91a71ac5c",
"type": "main",
"index": 0
}
]
]
},
"3b18d784-eded-4b74-ac44-b25565049e13": {
"main": [
[
{
"node": "96eadd32-17c2-44b0-a00b-8e2ddcecaafa",
"type": "main",
"index": 0
}
]
]
},
"caafd6dd-a2b2-405d-a078-cea3bb615788": {
"main": [
[
{
"node": "6db219fd-f54d-4bf8-b150-9c4f3069cf92",
"type": "main",
"index": 0
}
]
]
},
"3d5ce6a8-bf05-4457-88e6-c5ad5a995b1d": {
"main": [
[
{
"node": "caafd6dd-a2b2-405d-a078-cea3bb615788",
"type": "main",
"index": 0
}
]
]
}
}
}よくある質問
このワークフローの使い方は？
上記のJSON設定コードをコピーし、n8nインスタンスで新しいワークフローを作成して「JSONからインポート」を選択、設定を貼り付けて認証情報を必要に応じて変更してください。
このワークフローはどんな場面に適していますか？
上級 - IT運用, セキュリティ運用
有料ですか？
このワークフローは完全無料です。ただし、ワークフローで使用するサードパーティサービス（OpenAI APIなど）は別途料金が発生する場合があります。
関連ワークフロー
Googleスプレッドシートからn8nユーザーの招待を自動化する
Googleスプレッドシートからn8nユーザーの招待を自動化
Set
Code
Merge
+
Set
Code
Merge
11 ノードbangank36
IT運用
↔️ Airtableのバッチ処理
Airtable 方面の批量更新/插入（ Sends faster + カット API コール数 ）
If
Set
Code
+
If
Set
Code
35 ノードSimon Mayerhofer
IT運用
n8nの更新
Telegram approval システムを使った Docker コンテナ更新の自動化
If
Set
Ssh
+
If
Set
Ssh
27 ノードJaber Zare
DevOps
Microsoft Teams会議分析をGPT-4.1、Outlook、Mem.aiを使用して自動化
GPT-4.1、Outlook、Mem.aiを使ってMicrosoft Teams会議の分析を自動化する
If
Set
Code
+
If
Set
Code
61 ノードWayne Simpson
人事
EnumX：サブドメイン自動DNSクエリとMarkdownエクスポート
HackerTarget APIとGmailを使用した自動化されたサブドメインDNSレコード照会
Set
Code
Gmail
+
Set
Code
Gmail
13 ノードAdnan Tariq
セキュリティ運用
NotionとTelegramを基にした自動SSL証明書モニタリングおよび定期更新
NotionおよびTelegramを使用したSSL証明書の自動監視と自動更新
If
Set
Ssh
+
If
Set
Ssh
21 ノードFrank Chen
セキュリティ運用
