Skip to content
Skills Library
DevOps & cloud · Tool integration

deploy

/deploy

Push a local .workflow.ts to n8n, verify remote state, and live-test (test URL by default; `--activate --prod` runs production test). Use when the user asks to deploy, push or ship an existing .workflow.ts file.

Licence
MIT
Last repository change
15.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Push a local .workflow.ts to n8n, verify remote state, and live-test (test URL by default; `--activate --prod` runs production test). Use when the user asks to deploy, push or ship an existing .workflow.ts file.

Arguments

/deploy <workflow-name>.workflow.ts [--activate] [--prod]
Original author description

Push a local .workflow.ts to n8n, verify remote state, and live-test (test URL by default; `--activate --prod` runs production test). Use when the user asks to deploy, push or ship an existing .workflow.ts file.

How it works

  1. Steps
  2. Safety
Original SKILL.md headings · 172 lines, 1,123 words
SKILL.md preview
---
name: deploy
description: Push a local .workflow.ts to n8n, verify remote state, and live-test (test URL by default; `--activate --prod` runs production test). Use when the user asks to deploy, push or ship an existing .workflow.ts file.
argument-hint: "<workflow-name>.workflow.ts [--activate] [--prod]"
user-invocable: true
allowed-tools: Read, Grep, Glob, Bash(npx:*), Bash(grep:*)
---

# Deploy Workflow

Push a local `.workflow.ts` to n8n via `n8nac`, verify remote state, run a live test.

> **Model-invocable, with a user gate on activation.** The push itself is guarded fail-closed by the
> PreToolUse hooks (env-gate, push-gate for drift, push-lint-gate) and lands as a draft — the
> published version stays live. That is why Claude may run this skill when the user asks to deploy
> in plain words. **Activation and the production test are the irreversible part:** run step 8 only
> when the user explicitly asked for it (`--activate` / `--prod` or "aktivieren" / "activate" in
> their request). Otherwise stop after step 7 and ask once whether to activate.
> (Before 5.6.2 the skill carried `disable-model-invocation: true`; CLAUDE.md routed plain-language
> deploy requests to it anyway, so they were refused.)

## Steps

### 1. Resolve workflow

- **File path** (e.g., `workflows/create-lead.workflow.ts`) — use directly
- **Workflow name** (e.g., `create lead`) — find matching `.workflow.ts` in `workflows/`

If `$ARGUMENTS` is provided, use it. Otherwise, ask the user.

### 2. Validate before push (mandatory)

```bash
npx n8nac skills validate workflows/<name>.workflow.ts --strict --json
```

If validation fails → **stop and report**. Do not push with validation errors. For interpreting
the error (false-positives, expression vs schema errors, auto-sanitization, bulk fixes), consult the
companion `n8n-architect` skill's Common Mistakes — n8nac's raw validator messages are often terse.

### 2b. Expect the push-lint gate (runs inside `push`, fail-closed)

`npx n8nac push` is wrapped by a PreToolUse hook that compiles the file and refuses the push when
(1) a node type or `typeVersion` is missing on the running instance, (2) a top-level parameter does
not exist for the node's `typeVersion` (n8n ignores it silently), or (3) the design lint fails —
no error strategy on a top-level workflow with external calls, `continueOnFail` without a downstream
error check, unwired error output, orphan node, unbalanced expression, `availableInMCP` not true.
Read the `BLOCK  <rule>  <node>  <message>` lines, fix the `.workflow.ts`, push again. Rules and
fix paths: [docs/rules/gates.md](../../docs/rules/gates.md). The bypass
(`N8N_AUTOPILOT_SKIP_LINT=1`) exists for the user, not for the agent.

### 3. Drift check (mandatory — enforced by push-gate hook)

```bash
# Extract workflow id from @workflow({ id: '...' }) in the file
WF_ID=$(grep -oE "id:[[:space:]]*['\"][A-Za-z0-9]{10,}['\"]" workflows/<name>.workflow.ts | head -1 | grep -oE "[A-Za-z0-9]{10,}")

# Refresh remote cache, then read sync status
npx n8nac fetch "$WF_ID"
npx n8nac list --search "$WF_ID" --json
```

Decision table:

| status | Action |
|---|---|
| `TRACKED` | Safe to push. Proceed to step 4. |
| `LOCAL_ONLY` | New workflow (no remote yet). Safe to push (no overwrite risk). |
| `CONFLICT` / `MODIFIED_BOTH` / `DIVERGED` | **STOP.** Remote was modified since last pull. To avoid re-typing your edit: `cp` the local file to `<file>.local-bak`, run `npx n8nac pull "$WF_ID"` (remote wins), then diff the backup against the pulled file and re-apply your change as a small patch, then re-validate. NEVER use `npx n8nac resolve --mode keep-current` without explicit user authorization — the push-gate hook will block it. |
| `REMOTE_ONLY` | Local file references a remote id but no local tracking entry. Run `npx n8nac pull "$WF_ID"` first. |
| `ARCHIVED` | Read-only. Stop. Tell the user to unarchive via n8n UI or create a new workflow. |

If the user has confirmed they want to discard the remote change:
```bash
N8N_AUTOPILOT_ALLOW_LOCAL_WINS=1 npx n8nac push workflows/<name>.workflow.ts --verify
```

### 4. Push + verify in one call

> **mcpTrigger check:** If the workflow contains `mcpTrigger`, the PreToolUse hook (`ensure-mcp-trigger-setting.sh`) auto-fixes `availableInMCP: false → true` on push and warns when the field is missing entirely — see the warning and patch the source file if needed.

> **`@workflow` description field (n8nac 1.7.0+):** Set `description` for better discoverability in `n8nac list` + n8n UI:
> ```typescript
> @workflow({ name: "My Workflow", description: "What it does in one sentence", settings: { ... } })
> ```

```bash
npx n8nac push workflows/<name>.workflow.ts --verify
```

`--verify` fetches the workflow after push and validates it against the local schema in one call. If verify fails → re-push.

### 5. Check credential presence

```bash
npx n8nac workflow credential-required <workflowId>
```

- **Exit 0:** all present → proceed to test
- **Exit 1:** credentials missing → report which credentials are needed, skip live test

### 6. Trigger classification + payload inference

```bash
npx n8nac test-plan <workflowId> --json
```

Extract `triggerType`, `testable`, `suggestedPayload`.

| Trigger | Testable via CLI? | Action |
|---|---|---|
| `webhook`, `chat`, `form` | yes | proceed to live test |
| `schedule`, `manual`, `errorTrigger` | no | skip CLI live test → run `/n8n-autopilot:test-manual <workflowId>` which resolves the UI URL, waits for the execution-id, and inspects the run for you |

### 7. Live test (test URL — no activation needed)

`n8nac test` calls the test URL (`/webhook-test/`) by default.

```bash
npx n8nac test <workflowId> --data '<suggestedPayload from step 6>'
# For GET/HEAD webhooks (workflow reads $json.query):
npx n8nac test <workflowId> --query '<suggestedPayload>'
```

- **Class A error (exit 0):** missing credentials / model → report to user, do not iterate.
- **Class B error (exit 1):** wiring error → fix → re-validate → re-push (`--verify`) → re-test (max 3 cycles).

### 8. Production test (optional, only with `--activate`)

Only if the user explicitly asked for activation (`--activate`, or said so in their request). If
they did not, do not activate — ask once after step 7 whether they want it.

If the user passes `--activate`:

1. Activate the workflow:
   ```bash
   npx n8nac workflow activate <workflowId>
   ```
2. Production test:
   ```bash
   npx n8nac test <workflowId> --prod --data '<payload>'
   ```
3. On success → workflow stays active.
4. On failure → deactivate via `npx n8nac workflow deactivate <workflowId>`, report error.

### 9. mcpTrigger publish notice (manual)

After a successful push, check whether the workflow uses `mcpTrigger`:

```bash
grep -l "mcpTrigger\|n8n-nodes-langchain.mcpTrigger" workflows/<name>.workflow.ts
```

If yes, resolve the user-facing URL via the CLI (do not string-concat `<host>/workflow/<id>`):

```bash
npx n8nac workflow present <workflowId> --json
```

Surface a prominent notice using that URL:

```
⚠️  MANUAL PUBLISH REQUIRED — mcpTrigger detected

The MCP endpoint will return 404 until the workflow is published.

Open n8n UI:  <url from `n8nac workflow present`>
Click:        "Publish" button
```

`n8nac push` writes a new draft. The previously-published version stays live, but its MCP endpoint may diverge from the new draft. Each push to an `mcpTrigger` workflow requires a fresh UI publish — n8nac cannot publish on your behalf.

## Safety

- Always validate before pushing.
- Workflows deploy as inactive by default. `n8nac test` uses the test URL, no activation needed.
- `--activate` + `--prod` tests against the production webhook URL — use with caution.
- Never activate or run the production test without an explicit user request — see the gate note at the top.

Versions

RepositoryScoreLicence
This page · neurawork-git/n8n-autopilot100MIT
zeitlos/lucity100AGPL-3.0
jeremylongshore/tons-of-skills-marketplace100MIT
zeitlos/lucity100AGPL-3.0
microsoft/power-platform-skills100MIT
friendlyinternet/nuxt-crouton100MIT
wraith-proxy/wraith-skills100MIT
jikig-ai/soleur100Apache-2.0
curiositech/windags-skills100Apache-2.0

Database snapshot: 13.11.2026 · package version 9664f5ac60af (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ship-prod
    Use when deploying qaskills.sh to production, verifying whether a deploy landed, or when a push to main did not show up on the live site, e.g. "deploy", "ship it", "push this live", "is prod updated?", "the site still shows the old version".
  • 95commit-push-deploy
    Commit, push, then deploy only if allowlisted infra already exists. Use for /commit-push-deploy, "commit push deploy", "deploy this". Must push. Never force-push. Never invent infra.
  • 100vercel-deploy
    Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns…
  • 100vercel-deploy
    Deploy applications and websites to Vercel instantly. Use when asked to \"Deploy my app\", \"Deploy this to production\", \"Create a preview deployment\", or \"Push this live\". No authentication required - returns preview URL and claimable deployment link.
  • 100deploy-verify
    Post-deploy smoke test across browser, Sentry, Supabase, Langfuse, and the public web. Use when "verify deploy", "smoke test production", "post-release check", or "ship or rollback". Deploy plus watch → workflow-ship-and-observe.
  • 95deploy-to-vercel
    Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.