claude-memory/graph/insights/insight-n8n-test-workflow-api-cannot-trigger-schedule-based-22d124.md

39 lines
1.2 KiB
Markdown

---
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-03-01T15:58:51.839215+00:00"
relations:
- target: c3070599-c723-4993-bada-3103e6f03e53
type: RELATED_TO
direction: incoming
strength: 0.77
edge_id: 0e0bbad1-952b-413b-ade8-9e9cd58d4465
- target: de4a3c65-6eb5-4f73-ad69-685dba0a7847
type: RELATED_TO
direction: incoming
strength: 0.83
edge_id: e3349a77-3b63-4acd-a4cd-ae3a61882888
---
# 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)