diff --git a/graph/insights/insight-n8n-test-workflow-api-cannot-trigger-schedule-based-22d124.md b/graph/insights/insight-n8n-test-workflow-api-cannot-trigger-schedule-based-22d124.md
new file mode 100644
index 00000000000..c8ed1c2325f
--- /dev/null
+++ b/graph/insights/insight-n8n-test-workflow-api-cannot-trigger-schedule-based-22d124.md
@@ -0,0 +1,27 @@
+---
+id: 22d124fd-34e9-4538-acef-9962642a0e54
+type: insight
+title: "Insight: n8n test_workflow API cannot trigger schedule-based workflows"
+tags: [n8n, mcp, api, limitation]
+importance: 0.5
+confidence: 0.8
+created: "2026-02-20T04:17:05.893034+00:00"
+updated: "2026-02-20T04:17:05.893034+00:00"
+---
+
+# n8n API Limitation: Schedule Triggers Not Testable via API
+
+## Observation
+The n8n MCP `n8n_test_workflow` tool (and the underlying n8n API) only works with externally-triggerable workflows. Supported trigger types:
+- Webhook
+- Form
+- Chat
+
+## Limitation
+Schedule-triggered workflows (e.g., cron, interval) **cannot** be executed on-demand via the API or MCP tools.
+
+## Workarounds
+- Wait for the next scheduled run
+- Manually test the SSH command chain outside n8n
+- Temporarily add a webhook trigger node to test, then remove it
+- Use the n8n UI "Execute Workflow" button (manual run from the editor)