n8n API

**Quick judgment** A strong, practical skill for teams already invested in n8n who want to control and monitor their n8n instance from OpenClaw. It mainly acts as a thin, well-documented bridge to the official n8n Public REST API and is best suited for operational automation rather than casual users. **Key strengths** - Exposes most core n8n capabilities you’d expect from the UI (workflows, executions, tags, credentials, projects). - Works with both self-hosted and n8n Cloud, configured via `N8N_API_BASE_URL` and `N8N_API_KEY`. - Documentation includes concrete curl examples for listing workflows, activating/deactivating them, listing and retrying executions, and running health checks. **Risks and limitations** - Requires an n8n plan with Public API enabled; it will not work during n8n’s free trial and will silently fail without valid base URL/API key. - Operations are powerful: activating workflows, retrying executions, or calling webhooks can have real production impact if misconfigured. - Reliability depends entirely on the target n8n instance (network, uptime, retention settings for executions), and the page does not clearly describe robust error handling or safety rails in the skill itself. - Execution and credential management via API must be handled carefully to avoid leaking secrets or triggering unintended flows. **Recommended scenarios** - You run n8n (self-hosted or cloud) in production and want OpenClaw to perform health checks, monitor failures, and trigger incident playbooks. - You want CI/CD-style automation around n8n workflows (activate/deactivate, sanity checks, or test triggers) as part of a broader automation pipeline. - You need a central orchestration layer (OpenClaw) that can treat n8n as one of several back-end services, using this skill as the integration point.