Parent: #2805
Reason: Teams use n8n for workflows (webhooks, CRMs, Slack, etc.). Agents need to trigger executions and check run status so "agent decides → n8n runs the workflow" or "agent checks if the workflow succeeded" works without manual steps.
Use case: "When the agent classifies a ticket as urgent, it triggers an n8n workflow that pages on-call and posts to Slack."
Scope (MVP):
- Trigger workflow execution (webhook or n8n API: execute workflow by ID)
- Get execution status (run ID, status: success/failed/running)
- Optional: list workflows (for discovery or dynamic trigger)
- Authentication: API key (n8n instance URL + key); credentialSpec + credentialStore
- README: scope, setup, usage; unit tests for trigger and status
Link: Sub-issue of Expand agent capabilities #2805.
Parent: #2805
Reason: Teams use n8n for workflows (webhooks, CRMs, Slack, etc.). Agents need to trigger executions and check run status so "agent decides → n8n runs the workflow" or "agent checks if the workflow succeeded" works without manual steps.
Use case: "When the agent classifies a ticket as urgent, it triggers an n8n workflow that pages on-call and posts to Slack."
Scope (MVP):
Link: Sub-issue of Expand agent capabilities #2805.