skilld
All skills
n8n-io avatar

/post-build-flow

@b37fdc2 official
by n8n - Workflow Automationn8n-io/n8n206k stars
60,960

Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.

Ask your Agent

Use this Skill: https://skilld.dev/gh/n8n-io/n8n/post-build-flow

This session only. Nothing lands on disk.

referencestrigger-input-data-shapes.md

≈367 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Per-trigger inputData shape

Used by verify-built-workflow, executions(action="run"), and checkpoint verification. The pin-data adapter spreads or wraps based on trigger type — passing the wrong shape gives null downstream values that look like an expression bug.

Form Trigger (n8n-nodes-base.formTrigger)

Flat field map, e.g. {name: "Alice", email: "a@b.c"}. The production Form Trigger emits each field directly on $json, so the builder's $json.<field> expressions are correct. Do NOT wrap in formFields — the adapter will reject the call.

Webhook (n8n-nodes-base.webhook)

The body payload, e.g. {event: "signup", userId: "..."}. The adapter wraps it under body, so downstream nodes reference $json.body.<field>.

Chat Trigger (@n8n/n8n-nodes-langchain.chatTrigger)

{chatInput: "user message"}.

Schedule Trigger (n8n-nodes-base.scheduleTrigger)

Omit inputData; the adapter emits synthetic timestamp fields.

Other event triggers

Linear, GitHub, Slack, MCP, and similar triggers: pass inputData matching the trigger's expected payload shape from the node type definition.

Debugging wrong null values

Do not patch a workflow first when verify returns null downstream values. Re-run verify with the corrected inputData shape. Only patch the workflow if the expression is wrong against the production trigger output shape (consult node descriptions), not the instanceAi pin data path.

Source: SKILL.md on GitHub

Third-party checks

No alerts12d3 checks · Risk SAFE
  • Gen Agent Trust Hub12d

    The skill automates workflow verification and setup for n8n. It includes instructions to suppress standard agent responses to optimize the user interface flow and processes untrusted data from workflow executions, which creates a surface for indirect prompt injection.

  • Socket12d

    No alerts

  • Snyk12d

    Risk: LOW · No issues

Provenance

Signed by skilld at b37fdc2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago

Capability

Other metadata
recommended_tools
[
  "ask-user",
  "verify-built-workflow",
  "workflows",
  "build-workflow",
  "executions"
]

Topics

  • Testing
  • n8n
  • workflow
  • verification
  • setup
  • orchestration
  • automation

README badge

README badge for n8n-io/n8n/post-build-flow

What it does

Handles workflow verification and setup in n8n after a workflow build completes, routing to verification tools when ready and opening inline setup cards for credential or config requirements. Use this skill after `build-workflow` succeeds or when the orchestrator sends workflow-verification-follow-up or workflow-setup-required messages.

Generated from the current SKILL.md.

Frequently asked

When should I load this skill?
Load this skill after build-workflow succeeds on a direct build, or when the current message contains workflow-verification-follow-up or workflow-setup-required. It handles post-build verification and setup routing automatically.
Do I need to publish a workflow before testing it?
No. Both executions(action="run") and verify-built-workflow inject inputData as the trigger's output, so the workflow does not need to be active or published to test it.
What happens if setup is deferred by the user?
If workflows(action="setup") returns deferred: true, respect that choice and do not retry with credentials(action="setup") or any other setup tool. The user will configure it later.
How do I know if a saved workflow actually matches what was requested?
After build-workflow succeeds, call workflows(action="get-json", workflowId) to inspect the persisted workflow and compare it to the requested outcome. Build success only means the workflow was saved, not that it is correct.
Should I ask the user to set up credentials before building?
No. Call credentials(action="list") first to see what's available, then build immediately. The builder preserves valid credentials and auto-mocks missing ones. Setup is routed automatically after verification based on the build outcome.

Generated from the current SKILL.md. These answers refresh after source changes.