[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-n8n-n8n-workflow-lifecycle-official":3,"mdc--k0ozrj-key":30,"related-org-n8n-n8n-workflow-lifecycle-official":1871,"related-repo-n8n-n8n-workflow-lifecycle-official":2030},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":20,"repoUrl":21,"updatedAt":22,"license":23,"forks":24,"topics":25,"repo":26,"sourceUrl":28,"mdContent":29},"n8n-workflow-lifecycle-official","design and organize n8n workflows","Use when starting, designing, organizing, finishing, or shipping an n8n workflow. Covers visual layout (sticky notes), descriptions that capture the *why*, node names, validation, testing, folders\u002Fprojects, and publishing. Triggers on create_workflow_from_code, update_workflow, validate_workflow, publish_workflow, archive_workflow, \"design\", \"lay out\", \"organize\", \"structure\", \"sticky\", \"describe this workflow\", \"ship\", \"deploy\", \"publish\", \"name this workflow\", or any folder\u002Fproject organization request.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},"n8n","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fn8n.png","n8n-io",[12,14,17],{"name":8,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Process Documentation","process-documentation",{"name":18,"slug":19,"type":13},"Workflow Automation","workflow-automation",319,"https:\u002F\u002Fgithub.com\u002Fn8n-io\u002Fskills","2026-07-24T05:37:45.034412",null,30,[],{"repoUrl":21,"stars":20,"forks":24,"topics":27,"description":23},[],"https:\u002F\u002Fgithub.com\u002Fn8n-io\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fn8n-workflow-lifecycle-official","---\nname: n8n-workflow-lifecycle-official\ndescription: Use when starting, designing, organizing, finishing, or shipping an n8n workflow. Covers visual layout (sticky notes), descriptions that capture the *why*, node names, validation, testing, folders\u002Fprojects, and publishing. Triggers on create_workflow_from_code, update_workflow, validate_workflow, publish_workflow, archive_workflow, \"design\", \"lay out\", \"organize\", \"structure\", \"sticky\", \"describe this workflow\", \"ship\", \"deploy\", \"publish\", \"name this workflow\", or any folder\u002Fproject organization request.\n---\n\n# n8n Workflow Lifecycle\n\n## The six stages\n\n1. **PLAN.** Gather requirements, ask clarifying questions, search for existing workflows \u002F sub-workflows that already do this.\n2. **BUILD.** Write SDK code (with skills: subworkflows, node-config, expressions, code-nodes; readability section below). Use `validate_node_config` as a side-channel for iteration, debugging, or small single-node edits: clean per-parameter errors without full-graph noise. Not a replacement for `validate_workflow` in VALIDATE.\n3. **VALIDATE.** `validate_workflow` + `get_workflow_details` for connections, then have the user verify per-node credentials and create anything you couldn't (missing credentials, folders, etc).\n4. **TEST.** `test_workflow` with `prepare_test_pin_data`; iterate until output matches intent.\n5. **PUBLISH.** `publish_workflow` only after stages 3 and 4 are clean.\n6. **HANDOFF.** Production handoff: how to trigger it, what it returns, what to watch, what they should know to use it well.\n\nSkipping a stage produces workflows that look done but break in production, or solve the wrong problem entirely. Three most common skips:\n\n- **Build before plan.** \"User asked for X, I'll start coding\" without confirming what X means, whether the same logic already exists as a sub-workflow, or which folder\u002Fproject it belongs in. Cheaper to ask one clarifying question than to rebuild after.\n- **Test before user-side wire-up.** Running `test_workflow` before the user has verified credentials per node hits the wrong service or 401s. Get the user-side setup done as part of VALIDATE.\n- **Publish without test.** Validation passing means the SDK is well-formed; it does NOT mean the workflow is correct.\n\n## Non-negotiables\n\n1. **Validate AND verify before publish.** Run `validate_workflow` on the SDK code, then `get_workflow_details` after every create\u002Fupdate to check the `connections` object. Validation alone misses silently dropped wires. `validate_node_config` is a separate per-node iteration tool, not a replacement for this step.\n2. **Surface known limitations to the user.** If folders, MCP access, or any other limitation blocks the request, say so explicitly and propose a path. Don't silently dump workflows at the wrong location or report success on a request you couldn't fully fulfill.\n3. **Ask before testing when not-auto-pinned downstreams have side effects.** `test_workflow` auto-pins triggers, credentialed nodes, and HTTP Request nodes. Everything else (Code, Edit Fields, If, Wait, Execute Command, file ops, sub-workflow calls, Data Tables) runs for real. Ask the user before running if any of those would fire user-visible side effects. See `references\u002FTESTING.md`.\n\n## Strong defaults\n\n- **Test before publish** with `test_workflow` + `prepare_test_pin_data`. See `references\u002FTESTING.md` for mocking by trigger type, pinning individual nodes, and the side-effect surface. Looser for internal one-off scripts you watch run.\n- **Always include a `description`** on `create_workflow_from_code`. 1-2 sentences capturing *what* and *why*. See \"Readability\" below.\n\n## Validation isn't enough\n\n`validate_workflow` runs schema and shape checks: missing parameters, type errors, references to non-existent nodes. It does **not** catch:\n\n- The `.to()`-inside-`.add()` connection trap (silent dropped wires)\n- Fan-outs collapsed to a single connection\n- Merge index off-by-one\n- Error outputs wired without `onError: 'continueErrorOutput'`\n- Parameters that are syntactically valid but semantically wrong (e.g., wrong sheet ID, wrong column name)\n\nValidation is necessary but not sufficient. The real gate is:\n\n1. `validate_workflow` passes.\n2. `get_workflow_details` returns a `connections` object that matches your intent.\n3. `test_workflow` produces the right output on representative pinned data.\n\nOnly then call `publish_workflow`.\n\nFor the full pre-publish checklist, see `references\u002FVALIDATION_CHECKLIST.md`.\n\n## Execution model\n\nn8n workflows execute **sequentially, left-to-right, top-to-bottom**. Branches that visually appear parallel on the canvas (fan-out from one source to multiple downstreams) run one after the other, ordered by the target nodes' Y-position on the canvas. There is no automatic concurrency.\n\nPractical consequences:\n\n- A fan-out to three slow HTTP calls runs in series; total latency is the sum, not the max.\n- \"Parallel\" branches share workflow state in execution order; downstream consumers see whatever the last branch left.\n- For real concurrency, dispatch sub-workflows with `mode: 'each'` and `waitForSubWorkflow: false`. See `n8n-loops-official` and `n8n-subworkflows-official`.\n\nThis is platform behavior, not an SDK quirk. Don't design fan-outs around assumed parallelism.\n\n## Naming conventions\n\nBad names compound: a workflow that's hard to find six months from now gets duplicated.\n\nFor full conventions (verb-noun patterns, capitalization, prefixes), read `references\u002FNAMING_CONVENTIONS.md`. Short version:\n\n- **Workflows:** verb-first, scoped. `Send weekly customer report` not `Customer report sender`.\n- **Nodes:** describe what they *do* in this workflow, not the node type. `Fetch active customers` not `Postgres1`.\n- **Sub-workflows:** plain descriptive name (`Parse RFC2822 date`); carry the category in tags (`subworkflow`, a domain tag, `tool`), not a name prefix. `search_workflows({ tags })` filters on them. See `n8n-subworkflows-official` `references\u002FNAMING_AND_DISCOVERY.md`.\n- **Tags:** the AI-side discovery mechanism (n8n 2.27.0+). The MCP lists (`list_tags`), filters (`search_workflows({ tags })`), and attaches them (`update_workflow` `addTags`\u002F`removeTags`, auto-creating unknown names). Lowercase, 2-4 per workflow. See `references\u002FNAMING_CONVENTIONS.md`.\n\n## Readability: descriptions, node groups, sticky notes, conventions\n\nFor any workflow over ~5 nodes, four levers carry the readability load:\n\n- **Workflow `description`: capture the *why*, including AI-derived context.** Two sentences: what it does and why it exists. Most importantly, capture context you had during conversation that won't otherwise survive into the file (the constraint that drove the design, why this approach over the alternative, the user's reason for asking). Otherwise it dies with the chat.\n- **Node groups: the only way to group nodes.** Partition the canvas into named groups, one per logical step (`Validate input`, `Enrich order`, `Notify`), via `update_workflow` `setNodeGroups` (n8n 2.28.0+). Group every logical step past ~10 nodes. Each group must be a connected, trigger-free run with a single entry and exit (n8n rejects anything else); collapsed, the workflow reads as its steps, not its nodes. Split a section too branchy to form one group into smaller groups that each qualify, or leave it ungrouped. Organization only, members run inline (reuse\u002Fisolation is a sub-workflow's job).\n\n  Each group also accepts an optional **`description`** string (shown when the group is collapsed). Use it to add a one-sentence summary of what the group does, especially useful for groups whose name alone doesn't convey the *why*. Blank or whitespace-only descriptions are ignored. Keep descriptions concise; they appear in a small collapsed label.\n\n- **Sticky notes: annotate, don't group.** Grouping is the node group's job (above). Sticky notes are a follow-up layer for context a group can't carry: a callout on a tricky section, a TODO, a warning, a note on the trigger. Use the `n8n-nodes-base.stickyNote` node with markdown `content` (`### Title` on the first line, 1-3 sentences of body) and an integer `color` 1-7. Pick a small palette and stick to it (e.g. gray\u002Fyellow for notes, red for warnings, pink for TODOs); random colors communicate nothing.\n- **Node `notes` for non-obvious config.** Explain *why* a workaround exists or a Code node does what it does. Don't annotate obvious nodes.\n\nPlus two notes:\n\n- **Match existing project conventions before introducing your own.** Skim a couple of nearby workflows via `search_workflows` + `get_workflow_details` and mirror the sticky palette, naming, and description style.\n- **Layout is auto-applied on create \u002F update.** SDK `position` values for non-sticky nodes are ignored. Stickies, node groups, and naming are your readability levers.\n\n## Folder limitations\n\nThe MCP can place a workflow into a folder that **already exists**. It cannot:\n\n- Create new folders\n- Move existing folders\n- Move existing workflows between folders\n\nIf the user asks for a folder that doesn't exist, **say so before building**. Don't silently create at the project root and report success. Surface options:\n\n1. User creates the folder manually, then you place workflows into it.\n2. Use a different existing folder.\n3. Confirm root-level placement is acceptable.\n\nFor the full protocol including detecting existing folders via `search_folders`, read `references\u002FFOLDER_LIMITATIONS.md`.\n\n## Per-workflow MCP access\n\nEach workflow has an `availableInMCP` flag. The default depends on who created it:\n\n- **Workflows created via the MCP** (`create_workflow_from_code`) default to **MCP-accessible**. No toggle step needed: you can find them via `search_workflows` and operate on them right away.\n- **Workflows created in the n8n UI** can default to off. Until the user flips the toggle, the workflow is invisible to you.\n\nThe #1 case where this bites: **the user built a workflow manually in the UI and now wants you to inspect or edit it, but you can't see it.** Before assuming it doesn't exist or you're searching the wrong project, ask the user to confirm MCP access is enabled.\n\nSub-workflows called via MCP: the caller can use them as code-level sub-workflows without the toggle. To invoke as MCP-exposed *tools*, the toggle is required (and is on by default for MCP-created sub-workflows).\n\nFor the full case-by-case guide and user-facing message, read `references\u002FMCP_ACCESS_PER_WORKFLOW.md`.\n\n## User-side wire-up (part of stage 3)\n\nThere are things the user has to do that you can't, and they need to be done before testing, otherwise the test fires against the wrong credential, hits a missing folder, or 401s. Surface these as a short list during VALIDATE, before TEST:\n\n- **Verify credentials per node.** `newCredential('Label')` is cosmetic. n8n auto-assigns the most recently edited credential of the right type, which silently picks the wrong one when the user has multiples (prod vs staging Gmail, two API keys). Tell them: \"open every node that uses a credential and confirm the right one is selected.\" See `n8n-credentials-and-security-official` non-negotiable #2.\n- **Create missing credentials.** If the user pasted a secret in chat or the workflow needs an account that doesn't exist yet, name the credential *type* and have them create it in the UI.\n- **Create missing folders.** The MCP can't create folders. If the user wanted a folder that doesn't exist, they create it before you can place the workflow there. See `references\u002FFOLDER_LIMITATIONS.md`.\n- **MCP access toggle for user created workflows.** Workflows you create via the MCP are MCP-accessible by default. The toggle only matters when the test depends on a UI-created workflow being callable from the MCP. See `references\u002FMCP_ACCESS_PER_WORKFLOW.md`.\n\nDon't proceed to TEST until these are confirmed done.\n\n## Handoff: production handoff (stage 6)\n\nAfter `publish_workflow` and a clean test, the workflow is technically live, but the user still needs enough context to actually *use* it in production. Treat this like the freelancer-to-customer handoff: short, structured, and oriented toward how they'll operate it from here.\n\nWhat to include:\n\n- **How it triggers.** Webhook URL (live now that it's published), schedule cadence + timezone, manual trigger button, sub-workflow caller, whichever applies. For webhooks, hand them the URL.\n- **What it returns \u002F where the data goes.** One sentence. \"Writes new rows to the `customers` table,\" \"responds JSON to the caller,\" \"fires the on-call Slack channel.\"\n- **How to invoke it for real, with an example.** \"Hit the webhook with `curl -X POST \u003Curl> -d '{...}'`,\" \"trigger manually from the UI,\" \"wait until 09:00 UTC for the first scheduled run.\"\n- **What to watch.** Failure modes that surface as alerts\u002Ferrors, rate-limit ceilings on upstream services, and where to look first when something breaks (executions tab, error workflow, audit log, etc.).\n- **MCP access status.** If you created the workflow via the MCP, it's already MCP-accessible. Let the user know they can revoke access in Settings if they want to lock it down. If they hand-built it in the UI, they need to flip MCP access on for any other agent to call it.\n- **Anything still pending on their side.** Secret rotation if a token was pasted in chat, follow-up wiring you couldn't reach, known TODOs left in stickies.\n\nKeep it tight: half a dozen bullets, not a wall of text. The user shouldn't have to ask \"ok, what now?\"\n\n## Reference files\n\n| File | Read when |\n|---|---|\n| `references\u002FNAMING_CONVENTIONS.md` | Naming a new workflow, sub-workflow, or node |\n| `references\u002FFOLDER_LIMITATIONS.md` | User mentions a folder, project structure, or wants workflows organized |\n| `references\u002FMCP_ACCESS_PER_WORKFLOW.md` | Building a workflow that you or another agent will call via MCP |\n| `references\u002FVALIDATION_CHECKLIST.md` | Just finished a workflow and about to call `publish_workflow` |\n| `references\u002FREVIEW_CHECKLIST.md` | Reviewing or auditing an existing workflow (any age, any author). Severity-tiered findings, distinct from the pre-publish validation checklist |\n| `references\u002FTESTING.md` | About to run `test_workflow` or `execute_workflow`, mocking trigger input, side-effect protocol |\n\n## Anti-patterns\n\n| Anti-pattern | What goes wrong | Fix |\n|---|---|---|\n| Calling `publish_workflow` without validating | Broken workflows reach production | Validate, verify connections, then test |\n| Creating workflows at root because the requested folder doesn't exist | Workflows get lost, and the user has to drag them manually | Surface the limitation *before* building |\n| Generic node names (`HTTP Request1`, `Set2`) | Workflows are unreadable a month later | Rename to describe the action |\n| Missing `description` on `create_workflow_from_code` | Workflow invisible in search, no context for maintainers | Always include 1-2 sentences |\n| Asking the user to flip the MCP access toggle on a workflow you created via the MCP | Wastes their time, agent-created workflows default to MCP-accessible | Only mention the toggle for UI-created workflows, or when the user wants to *revoke* MCP access on an agent-created one |\n| Running `test_workflow` on a workflow with side-effecty non-pinned downstreams without asking | Real Data Table write, real sub-workflow side effects, real Execute Command output, etc. Triggers + credentialed nodes + HTTP get pinned, nothing else does | Ask first. See `references\u002FTESTING.md`. |\n| No node groups on a 15-node workflow | Reader has to read every node to find what they want | Group each logical step via `setNodeGroups`. See \"Readability\" above |\n| Sticky note used to fake a group, or sticky-of-every-color | Grouping is the node group's job \u002F color becomes pure noise | Group with `setNodeGroups`; reserve stickies for callouts, one color per category |\n| `description: \"Sends Slack.\"` | Adds nothing visible from the trigger and Slack node | Include *why* + AI-derived context: \"Sends weekly summary to founders. Replaces manual report that kept getting skipped.\" |\n| Designing fan-out branches as if they execute concurrently | n8n runs fan-out branches sequentially, top-to-bottom by Y-position. Total runtime is the sum of branches, not the max | For real concurrency, dispatch via `Execute Workflow` with `mode: 'each'` + `waitForSubWorkflow: false`. See `n8n-subworkflows-official` \"Fire-and-forget parallelization\" |\n",{"data":31,"body":32},{"name":4,"description":6},{"type":33,"children":34},"root",[35,44,51,171,177,218,224,300,306,377,383,400,450,455,495,506,518,524,536,541,587,592,598,603,616,784,790,795,956,961,1006,1012,1024,1042,1054,1072,1092,1098,1111,1154,1166,1178,1190,1196,1201,1278,1283,1289,1308,1313,1392,1397,1403,1548,1554],{"type":36,"tag":37,"props":38,"children":40},"element","h1",{"id":39},"n8n-workflow-lifecycle",[41],{"type":42,"value":43},"text","n8n Workflow Lifecycle",{"type":36,"tag":45,"props":46,"children":48},"h2",{"id":47},"the-six-stages",[49],{"type":42,"value":50},"The six stages",{"type":36,"tag":52,"props":53,"children":54},"ol",{},[55,67,94,119,144,161],{"type":36,"tag":56,"props":57,"children":58},"li",{},[59,65],{"type":36,"tag":60,"props":61,"children":62},"strong",{},[63],{"type":42,"value":64},"PLAN.",{"type":42,"value":66}," Gather requirements, ask clarifying questions, search for existing workflows \u002F sub-workflows that already do this.",{"type":36,"tag":56,"props":68,"children":69},{},[70,75,77,84,86,92],{"type":36,"tag":60,"props":71,"children":72},{},[73],{"type":42,"value":74},"BUILD.",{"type":42,"value":76}," Write SDK code (with skills: subworkflows, node-config, expressions, code-nodes; readability section below). Use ",{"type":36,"tag":78,"props":79,"children":81},"code",{"className":80},[],[82],{"type":42,"value":83},"validate_node_config",{"type":42,"value":85}," as a side-channel for iteration, debugging, or small single-node edits: clean per-parameter errors without full-graph noise. Not a replacement for ",{"type":36,"tag":78,"props":87,"children":89},{"className":88},[],[90],{"type":42,"value":91},"validate_workflow",{"type":42,"value":93}," in VALIDATE.",{"type":36,"tag":56,"props":95,"children":96},{},[97,102,104,109,111,117],{"type":36,"tag":60,"props":98,"children":99},{},[100],{"type":42,"value":101},"VALIDATE.",{"type":42,"value":103}," ",{"type":36,"tag":78,"props":105,"children":107},{"className":106},[],[108],{"type":42,"value":91},{"type":42,"value":110}," + ",{"type":36,"tag":78,"props":112,"children":114},{"className":113},[],[115],{"type":42,"value":116},"get_workflow_details",{"type":42,"value":118}," for connections, then have the user verify per-node credentials and create anything you couldn't (missing credentials, folders, etc).",{"type":36,"tag":56,"props":120,"children":121},{},[122,127,128,134,136,142],{"type":36,"tag":60,"props":123,"children":124},{},[125],{"type":42,"value":126},"TEST.",{"type":42,"value":103},{"type":36,"tag":78,"props":129,"children":131},{"className":130},[],[132],{"type":42,"value":133},"test_workflow",{"type":42,"value":135}," with ",{"type":36,"tag":78,"props":137,"children":139},{"className":138},[],[140],{"type":42,"value":141},"prepare_test_pin_data",{"type":42,"value":143},"; iterate until output matches intent.",{"type":36,"tag":56,"props":145,"children":146},{},[147,152,153,159],{"type":36,"tag":60,"props":148,"children":149},{},[150],{"type":42,"value":151},"PUBLISH.",{"type":42,"value":103},{"type":36,"tag":78,"props":154,"children":156},{"className":155},[],[157],{"type":42,"value":158},"publish_workflow",{"type":42,"value":160}," only after stages 3 and 4 are clean.",{"type":36,"tag":56,"props":162,"children":163},{},[164,169],{"type":36,"tag":60,"props":165,"children":166},{},[167],{"type":42,"value":168},"HANDOFF.",{"type":42,"value":170}," Production handoff: how to trigger it, what it returns, what to watch, what they should know to use it well.",{"type":36,"tag":172,"props":173,"children":174},"p",{},[175],{"type":42,"value":176},"Skipping a stage produces workflows that look done but break in production, or solve the wrong problem entirely. Three most common skips:",{"type":36,"tag":178,"props":179,"children":180},"ul",{},[181,191,208],{"type":36,"tag":56,"props":182,"children":183},{},[184,189],{"type":36,"tag":60,"props":185,"children":186},{},[187],{"type":42,"value":188},"Build before plan.",{"type":42,"value":190}," \"User asked for X, I'll start coding\" without confirming what X means, whether the same logic already exists as a sub-workflow, or which folder\u002Fproject it belongs in. Cheaper to ask one clarifying question than to rebuild after.",{"type":36,"tag":56,"props":192,"children":193},{},[194,199,201,206],{"type":36,"tag":60,"props":195,"children":196},{},[197],{"type":42,"value":198},"Test before user-side wire-up.",{"type":42,"value":200}," Running ",{"type":36,"tag":78,"props":202,"children":204},{"className":203},[],[205],{"type":42,"value":133},{"type":42,"value":207}," before the user has verified credentials per node hits the wrong service or 401s. Get the user-side setup done as part of VALIDATE.",{"type":36,"tag":56,"props":209,"children":210},{},[211,216],{"type":36,"tag":60,"props":212,"children":213},{},[214],{"type":42,"value":215},"Publish without test.",{"type":42,"value":217}," Validation passing means the SDK is well-formed; it does NOT mean the workflow is correct.",{"type":36,"tag":45,"props":219,"children":221},{"id":220},"non-negotiables",[222],{"type":42,"value":223},"Non-negotiables",{"type":36,"tag":52,"props":225,"children":226},{},[227,266,276],{"type":36,"tag":56,"props":228,"children":229},{},[230,235,237,242,244,249,251,257,259,264],{"type":36,"tag":60,"props":231,"children":232},{},[233],{"type":42,"value":234},"Validate AND verify before publish.",{"type":42,"value":236}," Run ",{"type":36,"tag":78,"props":238,"children":240},{"className":239},[],[241],{"type":42,"value":91},{"type":42,"value":243}," on the SDK code, then ",{"type":36,"tag":78,"props":245,"children":247},{"className":246},[],[248],{"type":42,"value":116},{"type":42,"value":250}," after every create\u002Fupdate to check the ",{"type":36,"tag":78,"props":252,"children":254},{"className":253},[],[255],{"type":42,"value":256},"connections",{"type":42,"value":258}," object. Validation alone misses silently dropped wires. ",{"type":36,"tag":78,"props":260,"children":262},{"className":261},[],[263],{"type":42,"value":83},{"type":42,"value":265}," is a separate per-node iteration tool, not a replacement for this step.",{"type":36,"tag":56,"props":267,"children":268},{},[269,274],{"type":36,"tag":60,"props":270,"children":271},{},[272],{"type":42,"value":273},"Surface known limitations to the user.",{"type":42,"value":275}," If folders, MCP access, or any other limitation blocks the request, say so explicitly and propose a path. Don't silently dump workflows at the wrong location or report success on a request you couldn't fully fulfill.",{"type":36,"tag":56,"props":277,"children":278},{},[279,284,285,290,292,298],{"type":36,"tag":60,"props":280,"children":281},{},[282],{"type":42,"value":283},"Ask before testing when not-auto-pinned downstreams have side effects.",{"type":42,"value":103},{"type":36,"tag":78,"props":286,"children":288},{"className":287},[],[289],{"type":42,"value":133},{"type":42,"value":291}," auto-pins triggers, credentialed nodes, and HTTP Request nodes. Everything else (Code, Edit Fields, If, Wait, Execute Command, file ops, sub-workflow calls, Data Tables) runs for real. Ask the user before running if any of those would fire user-visible side effects. See ",{"type":36,"tag":78,"props":293,"children":295},{"className":294},[],[296],{"type":42,"value":297},"references\u002FTESTING.md",{"type":42,"value":299},".",{"type":36,"tag":45,"props":301,"children":303},{"id":302},"strong-defaults",[304],{"type":42,"value":305},"Strong defaults",{"type":36,"tag":178,"props":307,"children":308},{},[309,338],{"type":36,"tag":56,"props":310,"children":311},{},[312,317,318,323,324,329,331,336],{"type":36,"tag":60,"props":313,"children":314},{},[315],{"type":42,"value":316},"Test before publish",{"type":42,"value":135},{"type":36,"tag":78,"props":319,"children":321},{"className":320},[],[322],{"type":42,"value":133},{"type":42,"value":110},{"type":36,"tag":78,"props":325,"children":327},{"className":326},[],[328],{"type":42,"value":141},{"type":42,"value":330},". See ",{"type":36,"tag":78,"props":332,"children":334},{"className":333},[],[335],{"type":42,"value":297},{"type":42,"value":337}," for mocking by trigger type, pinning individual nodes, and the side-effect surface. Looser for internal one-off scripts you watch run.",{"type":36,"tag":56,"props":339,"children":340},{},[341,352,354,360,362,368,370,375],{"type":36,"tag":60,"props":342,"children":343},{},[344,346],{"type":42,"value":345},"Always include a ",{"type":36,"tag":78,"props":347,"children":349},{"className":348},[],[350],{"type":42,"value":351},"description",{"type":42,"value":353}," on ",{"type":36,"tag":78,"props":355,"children":357},{"className":356},[],[358],{"type":42,"value":359},"create_workflow_from_code",{"type":42,"value":361},". 1-2 sentences capturing ",{"type":36,"tag":363,"props":364,"children":365},"em",{},[366],{"type":42,"value":367},"what",{"type":42,"value":369}," and ",{"type":36,"tag":363,"props":371,"children":372},{},[373],{"type":42,"value":374},"why",{"type":42,"value":376},". See \"Readability\" below.",{"type":36,"tag":45,"props":378,"children":380},{"id":379},"validation-isnt-enough",[381],{"type":42,"value":382},"Validation isn't enough",{"type":36,"tag":172,"props":384,"children":385},{},[386,391,393,398],{"type":36,"tag":78,"props":387,"children":389},{"className":388},[],[390],{"type":42,"value":91},{"type":42,"value":392}," runs schema and shape checks: missing parameters, type errors, references to non-existent nodes. It does ",{"type":36,"tag":60,"props":394,"children":395},{},[396],{"type":42,"value":397},"not",{"type":42,"value":399}," catch:",{"type":36,"tag":178,"props":401,"children":402},{},[403,424,429,434,445],{"type":36,"tag":56,"props":404,"children":405},{},[406,408,414,416,422],{"type":42,"value":407},"The ",{"type":36,"tag":78,"props":409,"children":411},{"className":410},[],[412],{"type":42,"value":413},".to()",{"type":42,"value":415},"-inside-",{"type":36,"tag":78,"props":417,"children":419},{"className":418},[],[420],{"type":42,"value":421},".add()",{"type":42,"value":423}," connection trap (silent dropped wires)",{"type":36,"tag":56,"props":425,"children":426},{},[427],{"type":42,"value":428},"Fan-outs collapsed to a single connection",{"type":36,"tag":56,"props":430,"children":431},{},[432],{"type":42,"value":433},"Merge index off-by-one",{"type":36,"tag":56,"props":435,"children":436},{},[437,439],{"type":42,"value":438},"Error outputs wired without ",{"type":36,"tag":78,"props":440,"children":442},{"className":441},[],[443],{"type":42,"value":444},"onError: 'continueErrorOutput'",{"type":36,"tag":56,"props":446,"children":447},{},[448],{"type":42,"value":449},"Parameters that are syntactically valid but semantically wrong (e.g., wrong sheet ID, wrong column name)",{"type":36,"tag":172,"props":451,"children":452},{},[453],{"type":42,"value":454},"Validation is necessary but not sufficient. The real gate is:",{"type":36,"tag":52,"props":456,"children":457},{},[458,468,485],{"type":36,"tag":56,"props":459,"children":460},{},[461,466],{"type":36,"tag":78,"props":462,"children":464},{"className":463},[],[465],{"type":42,"value":91},{"type":42,"value":467}," passes.",{"type":36,"tag":56,"props":469,"children":470},{},[471,476,478,483],{"type":36,"tag":78,"props":472,"children":474},{"className":473},[],[475],{"type":42,"value":116},{"type":42,"value":477}," returns a ",{"type":36,"tag":78,"props":479,"children":481},{"className":480},[],[482],{"type":42,"value":256},{"type":42,"value":484}," object that matches your intent.",{"type":36,"tag":56,"props":486,"children":487},{},[488,493],{"type":36,"tag":78,"props":489,"children":491},{"className":490},[],[492],{"type":42,"value":133},{"type":42,"value":494}," produces the right output on representative pinned data.",{"type":36,"tag":172,"props":496,"children":497},{},[498,500,505],{"type":42,"value":499},"Only then call ",{"type":36,"tag":78,"props":501,"children":503},{"className":502},[],[504],{"type":42,"value":158},{"type":42,"value":299},{"type":36,"tag":172,"props":507,"children":508},{},[509,511,517],{"type":42,"value":510},"For the full pre-publish checklist, see ",{"type":36,"tag":78,"props":512,"children":514},{"className":513},[],[515],{"type":42,"value":516},"references\u002FVALIDATION_CHECKLIST.md",{"type":42,"value":299},{"type":36,"tag":45,"props":519,"children":521},{"id":520},"execution-model",[522],{"type":42,"value":523},"Execution model",{"type":36,"tag":172,"props":525,"children":526},{},[527,529,534],{"type":42,"value":528},"n8n workflows execute ",{"type":36,"tag":60,"props":530,"children":531},{},[532],{"type":42,"value":533},"sequentially, left-to-right, top-to-bottom",{"type":42,"value":535},". Branches that visually appear parallel on the canvas (fan-out from one source to multiple downstreams) run one after the other, ordered by the target nodes' Y-position on the canvas. There is no automatic concurrency.",{"type":36,"tag":172,"props":537,"children":538},{},[539],{"type":42,"value":540},"Practical consequences:",{"type":36,"tag":178,"props":542,"children":543},{},[544,549,554],{"type":36,"tag":56,"props":545,"children":546},{},[547],{"type":42,"value":548},"A fan-out to three slow HTTP calls runs in series; total latency is the sum, not the max.",{"type":36,"tag":56,"props":550,"children":551},{},[552],{"type":42,"value":553},"\"Parallel\" branches share workflow state in execution order; downstream consumers see whatever the last branch left.",{"type":36,"tag":56,"props":555,"children":556},{},[557,559,565,566,572,573,579,580,586],{"type":42,"value":558},"For real concurrency, dispatch sub-workflows with ",{"type":36,"tag":78,"props":560,"children":562},{"className":561},[],[563],{"type":42,"value":564},"mode: 'each'",{"type":42,"value":369},{"type":36,"tag":78,"props":567,"children":569},{"className":568},[],[570],{"type":42,"value":571},"waitForSubWorkflow: false",{"type":42,"value":330},{"type":36,"tag":78,"props":574,"children":576},{"className":575},[],[577],{"type":42,"value":578},"n8n-loops-official",{"type":42,"value":369},{"type":36,"tag":78,"props":581,"children":583},{"className":582},[],[584],{"type":42,"value":585},"n8n-subworkflows-official",{"type":42,"value":299},{"type":36,"tag":172,"props":588,"children":589},{},[590],{"type":42,"value":591},"This is platform behavior, not an SDK quirk. Don't design fan-outs around assumed parallelism.",{"type":36,"tag":45,"props":593,"children":595},{"id":594},"naming-conventions",[596],{"type":42,"value":597},"Naming conventions",{"type":36,"tag":172,"props":599,"children":600},{},[601],{"type":42,"value":602},"Bad names compound: a workflow that's hard to find six months from now gets duplicated.",{"type":36,"tag":172,"props":604,"children":605},{},[606,608,614],{"type":42,"value":607},"For full conventions (verb-noun patterns, capitalization, prefixes), read ",{"type":36,"tag":78,"props":609,"children":611},{"className":610},[],[612],{"type":42,"value":613},"references\u002FNAMING_CONVENTIONS.md",{"type":42,"value":615},". Short version:",{"type":36,"tag":178,"props":617,"children":618},{},[619,644,675,730],{"type":36,"tag":56,"props":620,"children":621},{},[622,627,629,635,637,643],{"type":36,"tag":60,"props":623,"children":624},{},[625],{"type":42,"value":626},"Workflows:",{"type":42,"value":628}," verb-first, scoped. ",{"type":36,"tag":78,"props":630,"children":632},{"className":631},[],[633],{"type":42,"value":634},"Send weekly customer report",{"type":42,"value":636}," not ",{"type":36,"tag":78,"props":638,"children":640},{"className":639},[],[641],{"type":42,"value":642},"Customer report sender",{"type":42,"value":299},{"type":36,"tag":56,"props":645,"children":646},{},[647,652,654,659,661,667,668,674],{"type":36,"tag":60,"props":648,"children":649},{},[650],{"type":42,"value":651},"Nodes:",{"type":42,"value":653}," describe what they ",{"type":36,"tag":363,"props":655,"children":656},{},[657],{"type":42,"value":658},"do",{"type":42,"value":660}," in this workflow, not the node type. ",{"type":36,"tag":78,"props":662,"children":664},{"className":663},[],[665],{"type":42,"value":666},"Fetch active customers",{"type":42,"value":636},{"type":36,"tag":78,"props":669,"children":671},{"className":670},[],[672],{"type":42,"value":673},"Postgres1",{"type":42,"value":299},{"type":36,"tag":56,"props":676,"children":677},{},[678,683,685,691,693,699,701,707,709,715,717,722,723,729],{"type":36,"tag":60,"props":679,"children":680},{},[681],{"type":42,"value":682},"Sub-workflows:",{"type":42,"value":684}," plain descriptive name (",{"type":36,"tag":78,"props":686,"children":688},{"className":687},[],[689],{"type":42,"value":690},"Parse RFC2822 date",{"type":42,"value":692},"); carry the category in tags (",{"type":36,"tag":78,"props":694,"children":696},{"className":695},[],[697],{"type":42,"value":698},"subworkflow",{"type":42,"value":700},", a domain tag, ",{"type":36,"tag":78,"props":702,"children":704},{"className":703},[],[705],{"type":42,"value":706},"tool",{"type":42,"value":708},"), not a name prefix. ",{"type":36,"tag":78,"props":710,"children":712},{"className":711},[],[713],{"type":42,"value":714},"search_workflows({ tags })",{"type":42,"value":716}," filters on them. See ",{"type":36,"tag":78,"props":718,"children":720},{"className":719},[],[721],{"type":42,"value":585},{"type":42,"value":103},{"type":36,"tag":78,"props":724,"children":726},{"className":725},[],[727],{"type":42,"value":728},"references\u002FNAMING_AND_DISCOVERY.md",{"type":42,"value":299},{"type":36,"tag":56,"props":731,"children":732},{},[733,738,740,746,748,753,755,761,762,768,770,776,778,783],{"type":36,"tag":60,"props":734,"children":735},{},[736],{"type":42,"value":737},"Tags:",{"type":42,"value":739}," the AI-side discovery mechanism (n8n 2.27.0+). The MCP lists (",{"type":36,"tag":78,"props":741,"children":743},{"className":742},[],[744],{"type":42,"value":745},"list_tags",{"type":42,"value":747},"), filters (",{"type":36,"tag":78,"props":749,"children":751},{"className":750},[],[752],{"type":42,"value":714},{"type":42,"value":754},"), and attaches them (",{"type":36,"tag":78,"props":756,"children":758},{"className":757},[],[759],{"type":42,"value":760},"update_workflow",{"type":42,"value":103},{"type":36,"tag":78,"props":763,"children":765},{"className":764},[],[766],{"type":42,"value":767},"addTags",{"type":42,"value":769},"\u002F",{"type":36,"tag":78,"props":771,"children":773},{"className":772},[],[774],{"type":42,"value":775},"removeTags",{"type":42,"value":777},", auto-creating unknown names). Lowercase, 2-4 per workflow. See ",{"type":36,"tag":78,"props":779,"children":781},{"className":780},[],[782],{"type":42,"value":613},{"type":42,"value":299},{"type":36,"tag":45,"props":785,"children":787},{"id":786},"readability-descriptions-node-groups-sticky-notes-conventions",[788],{"type":42,"value":789},"Readability: descriptions, node groups, sticky notes, conventions",{"type":36,"tag":172,"props":791,"children":792},{},[793],{"type":42,"value":794},"For any workflow over ~5 nodes, four levers carry the readability load:",{"type":36,"tag":178,"props":796,"children":797},{},[798,821,890,932],{"type":36,"tag":56,"props":799,"children":800},{},[801,819],{"type":36,"tag":60,"props":802,"children":803},{},[804,806,811,813,817],{"type":42,"value":805},"Workflow ",{"type":36,"tag":78,"props":807,"children":809},{"className":808},[],[810],{"type":42,"value":351},{"type":42,"value":812},": capture the ",{"type":36,"tag":363,"props":814,"children":815},{},[816],{"type":42,"value":374},{"type":42,"value":818},", including AI-derived context.",{"type":42,"value":820}," Two sentences: what it does and why it exists. Most importantly, capture context you had during conversation that won't otherwise survive into the file (the constraint that drove the design, why this approach over the alternative, the user's reason for asking). Otherwise it dies with the chat.",{"type":36,"tag":56,"props":822,"children":823},{},[824,829,831,837,839,845,846,852,854,859,860,866,868,872,874,882,884,888],{"type":36,"tag":60,"props":825,"children":826},{},[827],{"type":42,"value":828},"Node groups: the only way to group nodes.",{"type":42,"value":830}," Partition the canvas into named groups, one per logical step (",{"type":36,"tag":78,"props":832,"children":834},{"className":833},[],[835],{"type":42,"value":836},"Validate input",{"type":42,"value":838},", ",{"type":36,"tag":78,"props":840,"children":842},{"className":841},[],[843],{"type":42,"value":844},"Enrich order",{"type":42,"value":838},{"type":36,"tag":78,"props":847,"children":849},{"className":848},[],[850],{"type":42,"value":851},"Notify",{"type":42,"value":853},"), via ",{"type":36,"tag":78,"props":855,"children":857},{"className":856},[],[858],{"type":42,"value":760},{"type":42,"value":103},{"type":36,"tag":78,"props":861,"children":863},{"className":862},[],[864],{"type":42,"value":865},"setNodeGroups",{"type":42,"value":867}," (n8n 2.28.0+). Group every logical step past ~10 nodes. Each group must be a connected, trigger-free run with a single entry and exit (n8n rejects anything else); collapsed, the workflow reads as its steps, not its nodes. Split a section too branchy to form one group into smaller groups that each qualify, or leave it ungrouped. Organization only, members run inline (reuse\u002Fisolation is a sub-workflow's job).",{"type":36,"tag":869,"props":870,"children":871},"br",{},[],{"type":42,"value":873},"Each group also accepts an optional ",{"type":36,"tag":60,"props":875,"children":876},{},[877],{"type":36,"tag":78,"props":878,"children":880},{"className":879},[],[881],{"type":42,"value":351},{"type":42,"value":883}," string (shown when the group is collapsed). Use it to add a one-sentence summary of what the group does, especially useful for groups whose name alone doesn't convey the ",{"type":36,"tag":363,"props":885,"children":886},{},[887],{"type":42,"value":374},{"type":42,"value":889},". Blank or whitespace-only descriptions are ignored. Keep descriptions concise; they appear in a small collapsed label.",{"type":36,"tag":56,"props":891,"children":892},{},[893,898,900,906,908,914,916,922,924,930],{"type":36,"tag":60,"props":894,"children":895},{},[896],{"type":42,"value":897},"Sticky notes: annotate, don't group.",{"type":42,"value":899}," Grouping is the node group's job (above). Sticky notes are a follow-up layer for context a group can't carry: a callout on a tricky section, a TODO, a warning, a note on the trigger. Use the ",{"type":36,"tag":78,"props":901,"children":903},{"className":902},[],[904],{"type":42,"value":905},"n8n-nodes-base.stickyNote",{"type":42,"value":907}," node with markdown ",{"type":36,"tag":78,"props":909,"children":911},{"className":910},[],[912],{"type":42,"value":913},"content",{"type":42,"value":915}," (",{"type":36,"tag":78,"props":917,"children":919},{"className":918},[],[920],{"type":42,"value":921},"### Title",{"type":42,"value":923}," on the first line, 1-3 sentences of body) and an integer ",{"type":36,"tag":78,"props":925,"children":927},{"className":926},[],[928],{"type":42,"value":929},"color",{"type":42,"value":931}," 1-7. Pick a small palette and stick to it (e.g. gray\u002Fyellow for notes, red for warnings, pink for TODOs); random colors communicate nothing.",{"type":36,"tag":56,"props":933,"children":934},{},[935,948,950,954],{"type":36,"tag":60,"props":936,"children":937},{},[938,940,946],{"type":42,"value":939},"Node ",{"type":36,"tag":78,"props":941,"children":943},{"className":942},[],[944],{"type":42,"value":945},"notes",{"type":42,"value":947}," for non-obvious config.",{"type":42,"value":949}," Explain ",{"type":36,"tag":363,"props":951,"children":952},{},[953],{"type":42,"value":374},{"type":42,"value":955}," a workaround exists or a Code node does what it does. Don't annotate obvious nodes.",{"type":36,"tag":172,"props":957,"children":958},{},[959],{"type":42,"value":960},"Plus two notes:",{"type":36,"tag":178,"props":962,"children":963},{},[964,988],{"type":36,"tag":56,"props":965,"children":966},{},[967,972,974,980,981,986],{"type":36,"tag":60,"props":968,"children":969},{},[970],{"type":42,"value":971},"Match existing project conventions before introducing your own.",{"type":42,"value":973}," Skim a couple of nearby workflows via ",{"type":36,"tag":78,"props":975,"children":977},{"className":976},[],[978],{"type":42,"value":979},"search_workflows",{"type":42,"value":110},{"type":36,"tag":78,"props":982,"children":984},{"className":983},[],[985],{"type":42,"value":116},{"type":42,"value":987}," and mirror the sticky palette, naming, and description style.",{"type":36,"tag":56,"props":989,"children":990},{},[991,996,998,1004],{"type":36,"tag":60,"props":992,"children":993},{},[994],{"type":42,"value":995},"Layout is auto-applied on create \u002F update.",{"type":42,"value":997}," SDK ",{"type":36,"tag":78,"props":999,"children":1001},{"className":1000},[],[1002],{"type":42,"value":1003},"position",{"type":42,"value":1005}," values for non-sticky nodes are ignored. Stickies, node groups, and naming are your readability levers.",{"type":36,"tag":45,"props":1007,"children":1009},{"id":1008},"folder-limitations",[1010],{"type":42,"value":1011},"Folder limitations",{"type":36,"tag":172,"props":1013,"children":1014},{},[1015,1017,1022],{"type":42,"value":1016},"The MCP can place a workflow into a folder that ",{"type":36,"tag":60,"props":1018,"children":1019},{},[1020],{"type":42,"value":1021},"already exists",{"type":42,"value":1023},". It cannot:",{"type":36,"tag":178,"props":1025,"children":1026},{},[1027,1032,1037],{"type":36,"tag":56,"props":1028,"children":1029},{},[1030],{"type":42,"value":1031},"Create new folders",{"type":36,"tag":56,"props":1033,"children":1034},{},[1035],{"type":42,"value":1036},"Move existing folders",{"type":36,"tag":56,"props":1038,"children":1039},{},[1040],{"type":42,"value":1041},"Move existing workflows between folders",{"type":36,"tag":172,"props":1043,"children":1044},{},[1045,1047,1052],{"type":42,"value":1046},"If the user asks for a folder that doesn't exist, ",{"type":36,"tag":60,"props":1048,"children":1049},{},[1050],{"type":42,"value":1051},"say so before building",{"type":42,"value":1053},". Don't silently create at the project root and report success. Surface options:",{"type":36,"tag":52,"props":1055,"children":1056},{},[1057,1062,1067],{"type":36,"tag":56,"props":1058,"children":1059},{},[1060],{"type":42,"value":1061},"User creates the folder manually, then you place workflows into it.",{"type":36,"tag":56,"props":1063,"children":1064},{},[1065],{"type":42,"value":1066},"Use a different existing folder.",{"type":36,"tag":56,"props":1068,"children":1069},{},[1070],{"type":42,"value":1071},"Confirm root-level placement is acceptable.",{"type":36,"tag":172,"props":1073,"children":1074},{},[1075,1077,1083,1085,1091],{"type":42,"value":1076},"For the full protocol including detecting existing folders via ",{"type":36,"tag":78,"props":1078,"children":1080},{"className":1079},[],[1081],{"type":42,"value":1082},"search_folders",{"type":42,"value":1084},", read ",{"type":36,"tag":78,"props":1086,"children":1088},{"className":1087},[],[1089],{"type":42,"value":1090},"references\u002FFOLDER_LIMITATIONS.md",{"type":42,"value":299},{"type":36,"tag":45,"props":1093,"children":1095},{"id":1094},"per-workflow-mcp-access",[1096],{"type":42,"value":1097},"Per-workflow MCP access",{"type":36,"tag":172,"props":1099,"children":1100},{},[1101,1103,1109],{"type":42,"value":1102},"Each workflow has an ",{"type":36,"tag":78,"props":1104,"children":1106},{"className":1105},[],[1107],{"type":42,"value":1108},"availableInMCP",{"type":42,"value":1110}," flag. The default depends on who created it:",{"type":36,"tag":178,"props":1112,"children":1113},{},[1114,1144],{"type":36,"tag":56,"props":1115,"children":1116},{},[1117,1122,1123,1128,1130,1135,1137,1142],{"type":36,"tag":60,"props":1118,"children":1119},{},[1120],{"type":42,"value":1121},"Workflows created via the MCP",{"type":42,"value":915},{"type":36,"tag":78,"props":1124,"children":1126},{"className":1125},[],[1127],{"type":42,"value":359},{"type":42,"value":1129},") default to ",{"type":36,"tag":60,"props":1131,"children":1132},{},[1133],{"type":42,"value":1134},"MCP-accessible",{"type":42,"value":1136},". No toggle step needed: you can find them via ",{"type":36,"tag":78,"props":1138,"children":1140},{"className":1139},[],[1141],{"type":42,"value":979},{"type":42,"value":1143}," and operate on them right away.",{"type":36,"tag":56,"props":1145,"children":1146},{},[1147,1152],{"type":36,"tag":60,"props":1148,"children":1149},{},[1150],{"type":42,"value":1151},"Workflows created in the n8n UI",{"type":42,"value":1153}," can default to off. Until the user flips the toggle, the workflow is invisible to you.",{"type":36,"tag":172,"props":1155,"children":1156},{},[1157,1159,1164],{"type":42,"value":1158},"The #1 case where this bites: ",{"type":36,"tag":60,"props":1160,"children":1161},{},[1162],{"type":42,"value":1163},"the user built a workflow manually in the UI and now wants you to inspect or edit it, but you can't see it.",{"type":42,"value":1165}," Before assuming it doesn't exist or you're searching the wrong project, ask the user to confirm MCP access is enabled.",{"type":36,"tag":172,"props":1167,"children":1168},{},[1169,1171,1176],{"type":42,"value":1170},"Sub-workflows called via MCP: the caller can use them as code-level sub-workflows without the toggle. To invoke as MCP-exposed ",{"type":36,"tag":363,"props":1172,"children":1173},{},[1174],{"type":42,"value":1175},"tools",{"type":42,"value":1177},", the toggle is required (and is on by default for MCP-created sub-workflows).",{"type":36,"tag":172,"props":1179,"children":1180},{},[1181,1183,1189],{"type":42,"value":1182},"For the full case-by-case guide and user-facing message, read ",{"type":36,"tag":78,"props":1184,"children":1186},{"className":1185},[],[1187],{"type":42,"value":1188},"references\u002FMCP_ACCESS_PER_WORKFLOW.md",{"type":42,"value":299},{"type":36,"tag":45,"props":1191,"children":1193},{"id":1192},"user-side-wire-up-part-of-stage-3",[1194],{"type":42,"value":1195},"User-side wire-up (part of stage 3)",{"type":36,"tag":172,"props":1197,"children":1198},{},[1199],{"type":42,"value":1200},"There are things the user has to do that you can't, and they need to be done before testing, otherwise the test fires against the wrong credential, hits a missing folder, or 401s. Surface these as a short list during VALIDATE, before TEST:",{"type":36,"tag":178,"props":1202,"children":1203},{},[1204,1229,1246,1262],{"type":36,"tag":56,"props":1205,"children":1206},{},[1207,1212,1213,1219,1221,1227],{"type":36,"tag":60,"props":1208,"children":1209},{},[1210],{"type":42,"value":1211},"Verify credentials per node.",{"type":42,"value":103},{"type":36,"tag":78,"props":1214,"children":1216},{"className":1215},[],[1217],{"type":42,"value":1218},"newCredential('Label')",{"type":42,"value":1220}," is cosmetic. n8n auto-assigns the most recently edited credential of the right type, which silently picks the wrong one when the user has multiples (prod vs staging Gmail, two API keys). Tell them: \"open every node that uses a credential and confirm the right one is selected.\" See ",{"type":36,"tag":78,"props":1222,"children":1224},{"className":1223},[],[1225],{"type":42,"value":1226},"n8n-credentials-and-security-official",{"type":42,"value":1228}," non-negotiable #2.",{"type":36,"tag":56,"props":1230,"children":1231},{},[1232,1237,1239,1244],{"type":36,"tag":60,"props":1233,"children":1234},{},[1235],{"type":42,"value":1236},"Create missing credentials.",{"type":42,"value":1238}," If the user pasted a secret in chat or the workflow needs an account that doesn't exist yet, name the credential ",{"type":36,"tag":363,"props":1240,"children":1241},{},[1242],{"type":42,"value":1243},"type",{"type":42,"value":1245}," and have them create it in the UI.",{"type":36,"tag":56,"props":1247,"children":1248},{},[1249,1254,1256,1261],{"type":36,"tag":60,"props":1250,"children":1251},{},[1252],{"type":42,"value":1253},"Create missing folders.",{"type":42,"value":1255}," The MCP can't create folders. If the user wanted a folder that doesn't exist, they create it before you can place the workflow there. See ",{"type":36,"tag":78,"props":1257,"children":1259},{"className":1258},[],[1260],{"type":42,"value":1090},{"type":42,"value":299},{"type":36,"tag":56,"props":1263,"children":1264},{},[1265,1270,1272,1277],{"type":36,"tag":60,"props":1266,"children":1267},{},[1268],{"type":42,"value":1269},"MCP access toggle for user created workflows.",{"type":42,"value":1271}," Workflows you create via the MCP are MCP-accessible by default. The toggle only matters when the test depends on a UI-created workflow being callable from the MCP. See ",{"type":36,"tag":78,"props":1273,"children":1275},{"className":1274},[],[1276],{"type":42,"value":1188},{"type":42,"value":299},{"type":36,"tag":172,"props":1279,"children":1280},{},[1281],{"type":42,"value":1282},"Don't proceed to TEST until these are confirmed done.",{"type":36,"tag":45,"props":1284,"children":1286},{"id":1285},"handoff-production-handoff-stage-6",[1287],{"type":42,"value":1288},"Handoff: production handoff (stage 6)",{"type":36,"tag":172,"props":1290,"children":1291},{},[1292,1294,1299,1301,1306],{"type":42,"value":1293},"After ",{"type":36,"tag":78,"props":1295,"children":1297},{"className":1296},[],[1298],{"type":42,"value":158},{"type":42,"value":1300}," and a clean test, the workflow is technically live, but the user still needs enough context to actually ",{"type":36,"tag":363,"props":1302,"children":1303},{},[1304],{"type":42,"value":1305},"use",{"type":42,"value":1307}," it in production. Treat this like the freelancer-to-customer handoff: short, structured, and oriented toward how they'll operate it from here.",{"type":36,"tag":172,"props":1309,"children":1310},{},[1311],{"type":42,"value":1312},"What to include:",{"type":36,"tag":178,"props":1314,"children":1315},{},[1316,1326,1344,1362,1372,1382],{"type":36,"tag":56,"props":1317,"children":1318},{},[1319,1324],{"type":36,"tag":60,"props":1320,"children":1321},{},[1322],{"type":42,"value":1323},"How it triggers.",{"type":42,"value":1325}," Webhook URL (live now that it's published), schedule cadence + timezone, manual trigger button, sub-workflow caller, whichever applies. For webhooks, hand them the URL.",{"type":36,"tag":56,"props":1327,"children":1328},{},[1329,1334,1336,1342],{"type":36,"tag":60,"props":1330,"children":1331},{},[1332],{"type":42,"value":1333},"What it returns \u002F where the data goes.",{"type":42,"value":1335}," One sentence. \"Writes new rows to the ",{"type":36,"tag":78,"props":1337,"children":1339},{"className":1338},[],[1340],{"type":42,"value":1341},"customers",{"type":42,"value":1343}," table,\" \"responds JSON to the caller,\" \"fires the on-call Slack channel.\"",{"type":36,"tag":56,"props":1345,"children":1346},{},[1347,1352,1354,1360],{"type":36,"tag":60,"props":1348,"children":1349},{},[1350],{"type":42,"value":1351},"How to invoke it for real, with an example.",{"type":42,"value":1353}," \"Hit the webhook with ",{"type":36,"tag":78,"props":1355,"children":1357},{"className":1356},[],[1358],{"type":42,"value":1359},"curl -X POST \u003Curl> -d '{...}'",{"type":42,"value":1361},",\" \"trigger manually from the UI,\" \"wait until 09:00 UTC for the first scheduled run.\"",{"type":36,"tag":56,"props":1363,"children":1364},{},[1365,1370],{"type":36,"tag":60,"props":1366,"children":1367},{},[1368],{"type":42,"value":1369},"What to watch.",{"type":42,"value":1371}," Failure modes that surface as alerts\u002Ferrors, rate-limit ceilings on upstream services, and where to look first when something breaks (executions tab, error workflow, audit log, etc.).",{"type":36,"tag":56,"props":1373,"children":1374},{},[1375,1380],{"type":36,"tag":60,"props":1376,"children":1377},{},[1378],{"type":42,"value":1379},"MCP access status.",{"type":42,"value":1381}," If you created the workflow via the MCP, it's already MCP-accessible. Let the user know they can revoke access in Settings if they want to lock it down. If they hand-built it in the UI, they need to flip MCP access on for any other agent to call it.",{"type":36,"tag":56,"props":1383,"children":1384},{},[1385,1390],{"type":36,"tag":60,"props":1386,"children":1387},{},[1388],{"type":42,"value":1389},"Anything still pending on their side.",{"type":42,"value":1391}," Secret rotation if a token was pasted in chat, follow-up wiring you couldn't reach, known TODOs left in stickies.",{"type":36,"tag":172,"props":1393,"children":1394},{},[1395],{"type":42,"value":1396},"Keep it tight: half a dozen bullets, not a wall of text. The user shouldn't have to ask \"ok, what now?\"",{"type":36,"tag":45,"props":1398,"children":1400},{"id":1399},"reference-files",[1401],{"type":42,"value":1402},"Reference files",{"type":36,"tag":1404,"props":1405,"children":1406},"table",{},[1407,1426],{"type":36,"tag":1408,"props":1409,"children":1410},"thead",{},[1411],{"type":36,"tag":1412,"props":1413,"children":1414},"tr",{},[1415,1421],{"type":36,"tag":1416,"props":1417,"children":1418},"th",{},[1419],{"type":42,"value":1420},"File",{"type":36,"tag":1416,"props":1422,"children":1423},{},[1424],{"type":42,"value":1425},"Read when",{"type":36,"tag":1427,"props":1428,"children":1429},"tbody",{},[1430,1447,1463,1479,1500,1517],{"type":36,"tag":1412,"props":1431,"children":1432},{},[1433,1442],{"type":36,"tag":1434,"props":1435,"children":1436},"td",{},[1437],{"type":36,"tag":78,"props":1438,"children":1440},{"className":1439},[],[1441],{"type":42,"value":613},{"type":36,"tag":1434,"props":1443,"children":1444},{},[1445],{"type":42,"value":1446},"Naming a new workflow, sub-workflow, or node",{"type":36,"tag":1412,"props":1448,"children":1449},{},[1450,1458],{"type":36,"tag":1434,"props":1451,"children":1452},{},[1453],{"type":36,"tag":78,"props":1454,"children":1456},{"className":1455},[],[1457],{"type":42,"value":1090},{"type":36,"tag":1434,"props":1459,"children":1460},{},[1461],{"type":42,"value":1462},"User mentions a folder, project structure, or wants workflows organized",{"type":36,"tag":1412,"props":1464,"children":1465},{},[1466,1474],{"type":36,"tag":1434,"props":1467,"children":1468},{},[1469],{"type":36,"tag":78,"props":1470,"children":1472},{"className":1471},[],[1473],{"type":42,"value":1188},{"type":36,"tag":1434,"props":1475,"children":1476},{},[1477],{"type":42,"value":1478},"Building a workflow that you or another agent will call via MCP",{"type":36,"tag":1412,"props":1480,"children":1481},{},[1482,1490],{"type":36,"tag":1434,"props":1483,"children":1484},{},[1485],{"type":36,"tag":78,"props":1486,"children":1488},{"className":1487},[],[1489],{"type":42,"value":516},{"type":36,"tag":1434,"props":1491,"children":1492},{},[1493,1495],{"type":42,"value":1494},"Just finished a workflow and about to call ",{"type":36,"tag":78,"props":1496,"children":1498},{"className":1497},[],[1499],{"type":42,"value":158},{"type":36,"tag":1412,"props":1501,"children":1502},{},[1503,1512],{"type":36,"tag":1434,"props":1504,"children":1505},{},[1506],{"type":36,"tag":78,"props":1507,"children":1509},{"className":1508},[],[1510],{"type":42,"value":1511},"references\u002FREVIEW_CHECKLIST.md",{"type":36,"tag":1434,"props":1513,"children":1514},{},[1515],{"type":42,"value":1516},"Reviewing or auditing an existing workflow (any age, any author). Severity-tiered findings, distinct from the pre-publish validation checklist",{"type":36,"tag":1412,"props":1518,"children":1519},{},[1520,1528],{"type":36,"tag":1434,"props":1521,"children":1522},{},[1523],{"type":36,"tag":78,"props":1524,"children":1526},{"className":1525},[],[1527],{"type":42,"value":297},{"type":36,"tag":1434,"props":1529,"children":1530},{},[1531,1533,1538,1540,1546],{"type":42,"value":1532},"About to run ",{"type":36,"tag":78,"props":1534,"children":1536},{"className":1535},[],[1537],{"type":42,"value":133},{"type":42,"value":1539}," or ",{"type":36,"tag":78,"props":1541,"children":1543},{"className":1542},[],[1544],{"type":42,"value":1545},"execute_workflow",{"type":42,"value":1547},", mocking trigger input, side-effect protocol",{"type":36,"tag":45,"props":1549,"children":1551},{"id":1550},"anti-patterns",[1552],{"type":42,"value":1553},"Anti-patterns",{"type":36,"tag":1404,"props":1555,"children":1556},{},[1557,1578],{"type":36,"tag":1408,"props":1558,"children":1559},{},[1560],{"type":36,"tag":1412,"props":1561,"children":1562},{},[1563,1568,1573],{"type":36,"tag":1416,"props":1564,"children":1565},{},[1566],{"type":42,"value":1567},"Anti-pattern",{"type":36,"tag":1416,"props":1569,"children":1570},{},[1571],{"type":42,"value":1572},"What goes wrong",{"type":36,"tag":1416,"props":1574,"children":1575},{},[1576],{"type":42,"value":1577},"Fix",{"type":36,"tag":1427,"props":1579,"children":1580},{},[1581,1606,1631,1664,1693,1718,1749,1774,1799,1827],{"type":36,"tag":1412,"props":1582,"children":1583},{},[1584,1596,1601],{"type":36,"tag":1434,"props":1585,"children":1586},{},[1587,1589,1594],{"type":42,"value":1588},"Calling ",{"type":36,"tag":78,"props":1590,"children":1592},{"className":1591},[],[1593],{"type":42,"value":158},{"type":42,"value":1595}," without validating",{"type":36,"tag":1434,"props":1597,"children":1598},{},[1599],{"type":42,"value":1600},"Broken workflows reach production",{"type":36,"tag":1434,"props":1602,"children":1603},{},[1604],{"type":42,"value":1605},"Validate, verify connections, then test",{"type":36,"tag":1412,"props":1607,"children":1608},{},[1609,1614,1619],{"type":36,"tag":1434,"props":1610,"children":1611},{},[1612],{"type":42,"value":1613},"Creating workflows at root because the requested folder doesn't exist",{"type":36,"tag":1434,"props":1615,"children":1616},{},[1617],{"type":42,"value":1618},"Workflows get lost, and the user has to drag them manually",{"type":36,"tag":1434,"props":1620,"children":1621},{},[1622,1624,1629],{"type":42,"value":1623},"Surface the limitation ",{"type":36,"tag":363,"props":1625,"children":1626},{},[1627],{"type":42,"value":1628},"before",{"type":42,"value":1630}," building",{"type":36,"tag":1412,"props":1632,"children":1633},{},[1634,1654,1659],{"type":36,"tag":1434,"props":1635,"children":1636},{},[1637,1639,1645,1646,1652],{"type":42,"value":1638},"Generic node names (",{"type":36,"tag":78,"props":1640,"children":1642},{"className":1641},[],[1643],{"type":42,"value":1644},"HTTP Request1",{"type":42,"value":838},{"type":36,"tag":78,"props":1647,"children":1649},{"className":1648},[],[1650],{"type":42,"value":1651},"Set2",{"type":42,"value":1653},")",{"type":36,"tag":1434,"props":1655,"children":1656},{},[1657],{"type":42,"value":1658},"Workflows are unreadable a month later",{"type":36,"tag":1434,"props":1660,"children":1661},{},[1662],{"type":42,"value":1663},"Rename to describe the action",{"type":36,"tag":1412,"props":1665,"children":1666},{},[1667,1683,1688],{"type":36,"tag":1434,"props":1668,"children":1669},{},[1670,1672,1677,1678],{"type":42,"value":1671},"Missing ",{"type":36,"tag":78,"props":1673,"children":1675},{"className":1674},[],[1676],{"type":42,"value":351},{"type":42,"value":353},{"type":36,"tag":78,"props":1679,"children":1681},{"className":1680},[],[1682],{"type":42,"value":359},{"type":36,"tag":1434,"props":1684,"children":1685},{},[1686],{"type":42,"value":1687},"Workflow invisible in search, no context for maintainers",{"type":36,"tag":1434,"props":1689,"children":1690},{},[1691],{"type":42,"value":1692},"Always include 1-2 sentences",{"type":36,"tag":1412,"props":1694,"children":1695},{},[1696,1701,1706],{"type":36,"tag":1434,"props":1697,"children":1698},{},[1699],{"type":42,"value":1700},"Asking the user to flip the MCP access toggle on a workflow you created via the MCP",{"type":36,"tag":1434,"props":1702,"children":1703},{},[1704],{"type":42,"value":1705},"Wastes their time, agent-created workflows default to MCP-accessible",{"type":36,"tag":1434,"props":1707,"children":1708},{},[1709,1711,1716],{"type":42,"value":1710},"Only mention the toggle for UI-created workflows, or when the user wants to ",{"type":36,"tag":363,"props":1712,"children":1713},{},[1714],{"type":42,"value":1715},"revoke",{"type":42,"value":1717}," MCP access on an agent-created one",{"type":36,"tag":1412,"props":1719,"children":1720},{},[1721,1733,1738],{"type":36,"tag":1434,"props":1722,"children":1723},{},[1724,1726,1731],{"type":42,"value":1725},"Running ",{"type":36,"tag":78,"props":1727,"children":1729},{"className":1728},[],[1730],{"type":42,"value":133},{"type":42,"value":1732}," on a workflow with side-effecty non-pinned downstreams without asking",{"type":36,"tag":1434,"props":1734,"children":1735},{},[1736],{"type":42,"value":1737},"Real Data Table write, real sub-workflow side effects, real Execute Command output, etc. Triggers + credentialed nodes + HTTP get pinned, nothing else does",{"type":36,"tag":1434,"props":1739,"children":1740},{},[1741,1743,1748],{"type":42,"value":1742},"Ask first. See ",{"type":36,"tag":78,"props":1744,"children":1746},{"className":1745},[],[1747],{"type":42,"value":297},{"type":42,"value":299},{"type":36,"tag":1412,"props":1750,"children":1751},{},[1752,1757,1762],{"type":36,"tag":1434,"props":1753,"children":1754},{},[1755],{"type":42,"value":1756},"No node groups on a 15-node workflow",{"type":36,"tag":1434,"props":1758,"children":1759},{},[1760],{"type":42,"value":1761},"Reader has to read every node to find what they want",{"type":36,"tag":1434,"props":1763,"children":1764},{},[1765,1767,1772],{"type":42,"value":1766},"Group each logical step via ",{"type":36,"tag":78,"props":1768,"children":1770},{"className":1769},[],[1771],{"type":42,"value":865},{"type":42,"value":1773},". See \"Readability\" above",{"type":36,"tag":1412,"props":1775,"children":1776},{},[1777,1782,1787],{"type":36,"tag":1434,"props":1778,"children":1779},{},[1780],{"type":42,"value":1781},"Sticky note used to fake a group, or sticky-of-every-color",{"type":36,"tag":1434,"props":1783,"children":1784},{},[1785],{"type":42,"value":1786},"Grouping is the node group's job \u002F color becomes pure noise",{"type":36,"tag":1434,"props":1788,"children":1789},{},[1790,1792,1797],{"type":42,"value":1791},"Group with ",{"type":36,"tag":78,"props":1793,"children":1795},{"className":1794},[],[1796],{"type":42,"value":865},{"type":42,"value":1798},"; reserve stickies for callouts, one color per category",{"type":36,"tag":1412,"props":1800,"children":1801},{},[1802,1811,1816],{"type":36,"tag":1434,"props":1803,"children":1804},{},[1805],{"type":36,"tag":78,"props":1806,"children":1808},{"className":1807},[],[1809],{"type":42,"value":1810},"description: \"Sends Slack.\"",{"type":36,"tag":1434,"props":1812,"children":1813},{},[1814],{"type":42,"value":1815},"Adds nothing visible from the trigger and Slack node",{"type":36,"tag":1434,"props":1817,"children":1818},{},[1819,1821,1825],{"type":42,"value":1820},"Include ",{"type":36,"tag":363,"props":1822,"children":1823},{},[1824],{"type":42,"value":374},{"type":42,"value":1826}," + AI-derived context: \"Sends weekly summary to founders. Replaces manual report that kept getting skipped.\"",{"type":36,"tag":1412,"props":1828,"children":1829},{},[1830,1835,1840],{"type":36,"tag":1434,"props":1831,"children":1832},{},[1833],{"type":42,"value":1834},"Designing fan-out branches as if they execute concurrently",{"type":36,"tag":1434,"props":1836,"children":1837},{},[1838],{"type":42,"value":1839},"n8n runs fan-out branches sequentially, top-to-bottom by Y-position. Total runtime is the sum of branches, not the max",{"type":36,"tag":1434,"props":1841,"children":1842},{},[1843,1845,1851,1852,1857,1858,1863,1864,1869],{"type":42,"value":1844},"For real concurrency, dispatch via ",{"type":36,"tag":78,"props":1846,"children":1848},{"className":1847},[],[1849],{"type":42,"value":1850},"Execute Workflow",{"type":42,"value":135},{"type":36,"tag":78,"props":1853,"children":1855},{"className":1854},[],[1856],{"type":42,"value":564},{"type":42,"value":110},{"type":36,"tag":78,"props":1859,"children":1861},{"className":1860},[],[1862],{"type":42,"value":571},{"type":42,"value":330},{"type":36,"tag":78,"props":1865,"children":1867},{"className":1866},[],[1868],{"type":42,"value":585},{"type":42,"value":1870}," \"Fire-and-forget parallelization\"",{"items":1872,"total":2029},[1873,1890,1907,1921,1933,1946,1959,1976,1985,1997,2007,2017],{"slug":1874,"name":1874,"fn":1875,"description":1876,"org":1877,"tags":1878,"stars":1887,"repoUrl":1888,"updatedAt":1889},"config-evals","configure workflow evaluations","Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it does not touch on-canvas evaluation nodes.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1879,1882,1883,1886],{"name":1880,"slug":1881,"type":13},"Evals","evals",{"name":8,"slug":8,"type":13},{"name":1884,"slug":1885,"type":13},"Testing","testing",{"name":18,"slug":19,"type":13},198156,"https:\u002F\u002Fgithub.com\u002Fn8n-io\u002Fn8n","2026-07-24T05:37:07.398695",{"slug":1891,"name":1891,"fn":1892,"description":1893,"org":1894,"tags":1895,"stars":1887,"repoUrl":1888,"updatedAt":1906},"credential-setup-with-computer-use","configure n8n credentials via browser","Guides n8n credential setup through Computer Use browser tools. Use when a user needs OAuth apps, API keys, client IDs, client secrets, or other credential values from an external service console.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1896,1899,1902,1903],{"name":1897,"slug":1898,"type":13},"Automation","automation",{"name":1900,"slug":1901,"type":13},"Configuration","configuration",{"name":8,"slug":8,"type":13},{"name":1904,"slug":1905,"type":13},"OAuth","oauth","2026-06-30T07:40:45.54",{"slug":1908,"name":1908,"fn":1909,"description":1910,"org":1911,"tags":1912,"stars":1887,"repoUrl":1888,"updatedAt":1920},"data-table-manager","manage n8n Data Tables","Load before calling data-tables or parse-file. Use for natural standalone requests like \"what data tables do I have?\", \"show\u002Flist my tables\", or \"what columns are in this table?\", and whenever the user asks to list, show, create, inspect, import, seed, query, update, clean up, rename columns in, or delete data tables and rows, especially from CSV\u002FXLSX\u002FJSON attachments. Also load before building or planning workflows that create or write to Data Tables (then load workflow-builder before build-workflow).",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1913,1916,1919],{"name":1914,"slug":1915,"type":13},"Data Engineering","data-engineering",{"name":1917,"slug":1918,"type":13},"Database","database",{"name":8,"slug":8,"type":13},"2026-07-27T06:07:14.648144",{"slug":1922,"name":1922,"fn":1923,"description":1924,"org":1925,"tags":1926,"stars":1887,"repoUrl":1888,"updatedAt":1906},"debugging-executions","debug failed n8n workflow executions","Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1927,1928,1931,1932],{"name":1897,"slug":1898,"type":13},{"name":1929,"slug":1930,"type":13},"Debugging","debugging",{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"slug":1934,"name":1934,"fn":1935,"description":1936,"org":1937,"tags":1938,"stars":1887,"repoUrl":1888,"updatedAt":1945},"intent-recognition","classify automation requests by control flow","Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embeds_other (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an agent tool). Must be used before deciding the intent of any automation request, including compound requests with multiple independent automations, mid-build extensions to an existing workflow or agent, one-off questions or reports that need external systems you cannot query directly, and requests that need clarification before an anchor can be chosen, before choosing workflow-builder, planning, or an agent-oriented design.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1939,1942,1943,1944],{"name":1940,"slug":1941,"type":13},"Agents","agents",{"name":1897,"slug":1898,"type":13},{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-07-30T05:30:06.772347",{"slug":1947,"name":1947,"fn":1948,"description":1949,"org":1950,"tags":1951,"stars":1887,"repoUrl":1888,"updatedAt":1958},"n8n-cli","manage n8n workflows from the CLI","Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1952,1953,1956,1957],{"name":1897,"slug":1898,"type":13},{"name":1954,"slug":1955,"type":13},"CLI","cli",{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-04-06T18:38:40.360123",{"slug":1960,"name":1960,"fn":1961,"description":1962,"org":1963,"tags":1964,"stars":1887,"repoUrl":1888,"updatedAt":1975},"n8n-docs-assistant","retrieve n8n documentation and guidance","Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Load n8n-docs via load_tool before calling it (search \"n8n docs\" if not visible). Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions opened from the credential modal.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1965,1968,1969,1972],{"name":1966,"slug":1967,"type":13},"Documentation","documentation",{"name":8,"slug":8,"type":13},{"name":1970,"slug":1971,"type":13},"Reference","reference",{"name":1973,"slug":1974,"type":13},"Search","search","2026-07-27T06:07:15.692906",{"slug":1977,"name":1977,"fn":1978,"description":1979,"org":1980,"tags":1981,"stars":1887,"repoUrl":1888,"updatedAt":1906},"planned-task-runtime","manage n8n task runtimes","Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1982,1983,1984],{"name":1897,"slug":1898,"type":13},{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"slug":1986,"name":1986,"fn":1987,"description":1988,"org":1989,"tags":1990,"stars":1887,"repoUrl":1888,"updatedAt":1996},"planning","coordinate multi-artifact workflows","ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema\u002Fmigration across tasks, or the user explicitly asked to review a plan first. Load create-tasks via load_tool before calling it (search \"create tasks\" if not visible). Do NOT use for new one-off workflows, single-workflow edits, verification-only requests, or standalone data-table ops — use workflow-builder or data-table-manager instead.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[1991,1992,1993,1995],{"name":1897,"slug":1898,"type":13},{"name":8,"slug":8,"type":13},{"name":1994,"slug":1986,"type":13},"Planning",{"name":18,"slug":19,"type":13},"2026-07-27T06:07:16.673218",{"slug":1998,"name":1998,"fn":1999,"description":2000,"org":2001,"tags":2002,"stars":1887,"repoUrl":1888,"updatedAt":2006},"post-build-flow","verify and set up n8n workflows","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\u002Fsetup follow-up turns.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2003,2004,2005],{"name":1897,"slug":1898,"type":13},{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-07-24T05:37:08.421329",{"slug":2008,"name":2008,"fn":2009,"description":2010,"org":2011,"tags":2012,"stars":1887,"repoUrl":1888,"updatedAt":2016},"workflow-builder","build and edit n8n workflows","Load before calling build-workflow. Default path for all single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, then call build-workflow with filePath. When the workflow creates or writes Data Tables, load data-table-manager first, then this skill. Do not load planning or create-tasks first. Load planning only when multiple coordinated workflows or shared cross-task data tables require a dependency-aware task graph.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2013,2014,2015],{"name":1897,"slug":1898,"type":13},{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-07-30T05:30:07.798011",{"slug":2018,"name":2018,"fn":2019,"description":2020,"org":2021,"tags":2022,"stars":20,"repoUrl":21,"updatedAt":2028},"n8n-agents-official","build AI agents in n8n","Use when building or editing any AI feature in n8n: AI Agents, Text Classifier, Information Extractor, Sentiment Analysis, Summarization Chain, Basic LLM Chain, embeddings, vector stores, single one-shot LLM calls, or AI media generation (image \u002F audio \u002F video) via the native LangChain provider nodes. Triggers on any `@n8n\u002Fn8n-nodes-langchain.*` node, \"agent\", \"chat assistant\", \"LLM with tools\", \"tool calling\", \"fromAi\", \"system prompt\", \"memory window\", \"structured output\", \"outputParser\", \"function calling\", \"RAG\", \"vector store\", \"embeddings\", \"classify with AI\", \"extract fields with LLM\", \"sentiment analysis\", \"summarize with LLM\", \"single LLM call\", chat triggers with files, AI image \u002F video \u002F audio generation, or any multi-turn or one-shot LLM behavior.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2023,2024,2027],{"name":1940,"slug":1941,"type":13},{"name":2025,"slug":2026,"type":13},"LLM","llm",{"name":18,"slug":19,"type":13},"2026-07-08T05:44:47.938896",25,{"items":2031,"total":2118},[2032,2038,2051,2067,2082,2094,2105],{"slug":2018,"name":2018,"fn":2019,"description":2020,"org":2033,"tags":2034,"stars":20,"repoUrl":21,"updatedAt":2028},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2035,2036,2037],{"name":1940,"slug":1941,"type":13},{"name":2025,"slug":2026,"type":13},{"name":18,"slug":19,"type":13},{"slug":2039,"name":2039,"fn":2040,"description":2041,"org":2042,"tags":2043,"stars":20,"repoUrl":21,"updatedAt":2050},"n8n-binary-and-data-official","handle binary data and files in n8n","Use when handling files, images, attachments, or binary data in n8n, OR when an AI agent needs to take a user-uploaded file as tool input or return a generated file. For Data Tables (schemas, dedup, persistent state), see the separate n8n-data-tables-official skill. Triggers on \"file\", \"image\", \"PDF\", \"attachment\", \"binary\", \"upload\", \"download\", chat trigger with files, agent tool that needs a file, vision\u002Fmultimodal, or any handling of non-JSON file data.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2044,2045,2048,2049],{"name":1897,"slug":1898,"type":13},{"name":2046,"slug":2047,"type":13},"File Uploads","file-uploads",{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-07-08T05:45:01.884342",{"slug":2052,"name":2052,"fn":2053,"description":2054,"org":2055,"tags":2056,"stars":20,"repoUrl":21,"updatedAt":2066},"n8n-code-nodes-official","write custom logic in n8n","Use when the user reaches for a Code node, mentions writing JavaScript or Python in n8n, or any custom logic comes up in workflow design. Triggers on \"Code node\", \"Code\", \"JavaScript\", \"Python\", \"custom logic\", \"transform data\", \"$input\", \"$json transformation\", \"loop in code\", \"write a function\", or any time the obvious answer seems to be \"just put it in code.\"",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2057,2060,2063],{"name":2058,"slug":2059,"type":13},"Engineering","engineering",{"name":2061,"slug":2062,"type":13},"JavaScript","javascript",{"name":2064,"slug":2065,"type":13},"Python","python","2026-07-08T05:44:49.656127",{"slug":1226,"name":1226,"fn":2068,"description":2069,"org":2070,"tags":2071,"stars":20,"repoUrl":21,"updatedAt":2081},"manage credentials and security in n8n","Use when handling any auth, API keys, tokens, OAuth, bearer tokens, basic auth, or secret values in n8n workflows. Triggers on \"API key\", \"token\", \"bearer\", \"OAuth\", \"secret\", \"auth\", \"credentials\", \"Authorization header\", \"x-api-key\", or any node configuration that mentions a third-party service.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2072,2075,2076,2077,2078],{"name":2073,"slug":2074,"type":13},"Authentication","authentication",{"name":1897,"slug":1898,"type":13},{"name":8,"slug":8,"type":13},{"name":1904,"slug":1905,"type":13},{"name":2079,"slug":2080,"type":13},"Security","security","2026-07-08T05:45:07.766252",{"slug":2083,"name":2083,"fn":1909,"description":2084,"org":2085,"tags":2086,"stars":20,"repoUrl":21,"updatedAt":2093},"n8n-data-tables-official","Use when working with n8n's built-in Data Tables, designing schemas, inserting\u002Fupdating\u002Fupserting rows, deduping, or querying. Triggers on \"Data Table\", \"data table\", `n8n-nodes-base.dataTable`, \"dedup\", \"idempotency\", \"lookup\", \"persistent state\", \"store across executions\", or any schema design discussion inside n8n.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2087,2090,2091,2092],{"name":2088,"slug":2089,"type":13},"Data Modeling","data-modeling",{"name":1917,"slug":1918,"type":13},{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-07-08T05:44:52.048039",{"slug":2095,"name":2095,"fn":2096,"description":2097,"org":2098,"tags":2099,"stars":20,"repoUrl":21,"updatedAt":2104},"n8n-debugging-official","debug and fix n8n workflow errors","Use when an n8n workflow isn't working, errors appear, results don't match what was expected, or the user says \"this isn't working.\" Triggers on errors, unexpected output, \"it's not working\", \"why is this happening\", \"the workflow stopped\", failure investigation, or any debugging context.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2100,2101,2102,2103],{"name":1897,"slug":1898,"type":13},{"name":1929,"slug":1930,"type":13},{"name":8,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-07-08T05:45:05.897341",{"slug":2106,"name":2106,"fn":2107,"description":2108,"org":2109,"tags":2110,"stars":20,"repoUrl":21,"updatedAt":2117},"n8n-error-handling-official","implement error handling in n8n","Use when building any webhook-triggered workflow, scheduled\u002Fproduction-bound workflow, wiring a per-node error output, or any workflow where silent failure would drop user-visible work. Triggers on \"webhook\", \"respond to webhook\", \"API\", \"production\", \"error\", \"failure\", \"5xx\", \"try\u002Fcatch\", \"error workflow\", \"onError\", \"continueErrorOutput\", \"error branch\", \"node error output\", \"output(1)\", \"main[1]\", \"scheduled\", or any workflow that runs unattended.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[2111,2112,2113,2116],{"name":1929,"slug":1930,"type":13},{"name":8,"slug":8,"type":13},{"name":2114,"slug":2115,"type":13},"Operations","operations",{"name":18,"slug":19,"type":13},"2026-07-08T05:44:59.710099",14]