n8n-workflow-ops

Validate and trigger n8n workflows via localhost:5678 with execution monitoring.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/williamsforeal/Cyclone-SS --skill n8n-workflow-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-workflow-ops
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/global-skills/n8n-workflow-ops
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill n8n-workflow-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

n8n workflow failures and import mistakes slow down automation, making it hard to trigger the right workflow, confirm execution status, and quickly validate JSON before it breaks production runs.

Core Features & Use Cases

  • List and inspect workflows: Retrieves available n8n workflows with details like names, webhook endpoints, credential needs, and modification/import status.
  • Validate workflow JSON before import: Checks workflow JSON structure (nodes, connections, name), extracts credential requirements, flags missing credentials from .env, and highlights placeholder values.
  • Trigger and monitor executions: Triggers webhook workflows, returns execution IDs immediately, and supports fetching execution details for debugging.

Quick Start

Ask the skill to list current n8n workflows, then trigger a specific workflow webhook and return the execution ID so you can monitor results.

Frequently Asked Questions about n8n-workflow-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate n8n workflow JSON before importing it?

Validate workflow JSON by checking node structures, connections, and names, extracting credential requirements, and flagging missing .env mappings or placeholder values to prevent import errors.

How do I trigger a webhook-based n8n workflow and get the execution ID?

Trigger webhook workflows by health-checking your local n8n instance and sending a webhook request, which immediately returns the execution ID for monitoring results.

Can I debug failed n8n workflow executions using an execution ID?

Debug failed workflow executions by querying the returned execution ID to fetch detailed execution logs and investigate specific failure points.

Do I need a local n8n instance running to list and inspect workflows?

You need a local n8n instance running at localhost:5678 to fetch available workflows and retrieve details like names, webhook endpoints, and credential needs.

What is the best way to discover existing n8n workflows and check their import status?

Discover existing workflows by listing them to retrieve details like names, webhook endpoints, credential needs, and modification or import status.

Why does my n8n workflow import fail due to missing credentials?

Workflow imports fail when credential requirements in the JSON are missing from your .env file or contain placeholder values, which validation checks flag before import.