skills.rest
icednut
icednutCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

n8n-studio:analyze-workflow-input

Analyze n8n workflow trigger input data from a past execution.

Updated Apr 10, 2026
Search Tags:#workflow analysis#test data#n8n#webhook payload#trigger data#execution id#summary json
One-click install
npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-analyze-workflow-input
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: n8n-studio:analyze-workflow-input
Source: https://github.com/icednut/n8n-studio/tree/main/skills/analyze-workflow-input
Command: npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-analyze-workflow-input

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand the exact trigger input data format of an existing n8n workflow by analyzing the data produced during a past execution.

Core Features & Use Cases

  • Execution-driven trigger inspection: Analyzes a past n8n Execution (by Execution ID) to derive the trigger node and its input/output structure.
  • Webhook-first automatic formatting: When the first node is a webhook-type trigger, it stores the webhook output sample data into summary as triggerDataFormat without any transformation.
  • Fallback for non-webhook triggers: When the first node is not a webhook trigger, it requests user-provided JSON as the triggerDataFormat source sample.
  • Summary persistence: Updates workflow summary at workflow/*/summary/[workflow_id].json by adding or updating triggerDataFormat, enabling later test-data generation.

Quick Start

Run n8n-studio:analyze-workflow-input with the Execution ID of the workflow run you want to inspect.

Frequently Asked Questions about n8n-studio:analyze-workflow-input

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

FAQPage Schema
How do I extract webhook payload data from a past n8n execution?▼

To extract webhook payload data from a past n8n execution, analyze the execution ID to locate the first webhook trigger node and store its unmodified output sample data into a summary JSON file. This captures the exact trigger input format for testing.

What is the process for reconstructing n8n trigger data for workflow documentation?▼

Reconstructing n8n trigger data involves fetching execution details using an execution ID and retrieving the workflow to locate the first trigger node. The system then writes the trigger input format into the workflow summary JSON for documentation.

How do I analyze n8n workflow trigger input when the first node is not a webhook?▼

When the first node is not a webhook trigger, analyzing n8n workflow trigger input requires you to provide a custom JSON sample. This user-provided JSON is then used as the source to define the triggerDataFormat in the summary.

Does n8n workflow input analysis require an execution ID?▼

Yes, n8n workflow input analysis requires an execution ID to fetch past execution details. This ID allows the system to identify the specific workflow run and extract the trigger node's input and output structure accurately.

Where does the analyzed n8n trigger data format get saved?▼

The analyzed n8n trigger data format gets saved directly into the workflow summary JSON file. Specifically, it updates or creates a triggerDataFormat field at workflow/*/summary/[workflow_id].json to enable later test data generation.

Related Skills

Explore More Software Engineering Skills→
icednuticednut

n8n-studio:analyze-workflow

Analyze n8n workflow structure and execution failures from summary JSON files.

Community
Intermediate
icednuticednut

n8n-studio:plan-tests

Generate unit and integration test scenarios from n8n workflow design documents.

Community
Intermediate
githubgithub
37.6k

mcp-cli

Execute MCP server tools with JSON payloads via CLI.

Official
Basic
pmcdowallpmcdowall

webhook-subscriptions

Create webhook subscriptions that trigger automated agent runs from external service events.

Community
Advanced