Move simple and medium Zaps to n8n (self-hosted or n8n Cloud)

I'm migrating a Zapier Zap to n8n (version {{n8n_version}}, self-hosted). Here is the Zap, step by step, including field mappings, filters and formatter settings:

{{zap_steps}}

Sample trigger payload (JSON, sensitive values redacted):
{{sample_payload}}

Give me:
1. A numbered list of n8n nodes (exact node names as they appear in n8n), with the settings to choose in each.
2. Every expression I need, in n8n syntax (e.g. {{ $json.email }} or {{ $('Node Name').item.json.field }}), mapped to the original Zap field.
3. Anything in this Zap with no direct n8n equivalent and how to handle it (HTTP Request node, Code node, or redesign).
4. Time zone, date-format and empty-field pitfalls specific to this Zap.
5. A test plan: which 3 sample inputs prove the n8n version matches the Zap.
If you're unsure whether a node or option exists in this n8n version, say so rather than inventing it.

Write JavaScript for an n8n Code node in mode "{{code_mode}}" ("Run Once for All Items" or "Run Once for Each Item").

Input items look like this (JSON):
{{input_example}}

Output items must look like this:
{{output_example}}

Transformation rules:
{{rules}}

Requirements: use $input.all() or $input.item as appropriate for the mode; return items in n8n's [{ json: {...} }] shape; no external npm packages; handle missing fields without throwing; add short comments. Then give two edge-case inputs and the expected outputs so I can test it.

An n8n workflow failed during a parallel run against the original Zap.

Node that failed: {{node_name}} ({{node_type}})
Error message: {{error_message}}
Input data to that node (redacted): {{node_input}}
What the Zapier version produced for the same trigger: {{zapier_output}}

Explain the most likely cause in plain English, give the exact fix (setting, expression or credential change), and tell me how to confirm it's fixed without triggering real side-effects (emails, payments, CRM writes).

# docker-compose.yml — n8n Community Edition behind Traefik (automatic HTTPS)
# Adapted from n8n's "Docker Compose" server-setup guide (docs.n8n.io, checked 2026-10-13).
# Changes from the docs example: pinned image tag, explicit N8N_ENCRYPTION_KEY,
# Traefik dashboard NOT exposed (the docs example sets --api.insecure=true).
#
# Login: n8n has NO basic-auth env vars any more — N8N_BASIC_AUTH_* were removed in n8n 1.0.
# Access is protected by n8n's own user management: the first visitor creates the OWNER account.
# So create the owner account immediately after first start (or firewall port 443 to your IP until you have).

services:
  traefik:
    image: "traefik:${TRAEFIK_VERSION}"
    restart: always
    command:
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.web.http.redirections.entryPoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--entrypoints.websecure.address=:443"
      - "--certificatesresolvers.mytlschallenge.acme.tlschallenge=true"
      - "--certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}"
      - "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json"
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - traefik_data:/letsencrypt
      - /var/run/docker.sock:/var/run/docker.sock:ro

  n8n:
    image: "n8nio/n8n:${N8N_VERSION}"     # pin a version; upgrade deliberately after reading release notes
    restart: always
    ports:
      - "127.0.0.1:5678:5678"             # only reachable through Traefik, not directly from the internet
    labels:
      - traefik.enable=true
      - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.entrypoints=web,websecure
      - traefik.http.routers.n8n.tls.certresolver=mytlschallenge
      - traefik.http.middlewares.n8n.headers.SSLRedirect=true
      - traefik.http.middlewares.n8n.headers.STSSeconds=315360000
      - traefik.http.middlewares.n8n.headers.browserXSSFilter=true
      - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
      - traefik.http.middlewares.n8n.headers.forceSTSHeader=true
      - traefik.http.middlewares.n8n.headers.SSLHost=${DOMAIN_NAME}
      - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
      - traefik.http.middlewares.n8n.headers.STSPreload=true
      - traefik.http.routers.n8n.middlewares=n8n@docker
    environment:
      - N8N_ENCRYPTION_KEY=${N8N_ENCRYPTION_KEY}   # encrypts stored credentials; back this up separately
      - N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - N8N_WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/  # n8n >= 2.30.0
      # - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/    # use this name instead on n8n < 2.30.0
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}                   # used by Schedule Trigger
      - TZ=${GENERIC_TIMEZONE}
      - N8N_RESTRICT_FILE_ACCESS_TO=/files
    volumes:
      - n8n_data:/home/node/.n8n      # SQLite database, encryption key, settings — THIS is what you back up
      - ./local-files:/files          # create this folder yourself before first start
      - ./backups:/backups            # target for `n8n export:*` backup commands

volumes:
  n8n_data:
  traefik_data:

# ---------------------------------------------------------------------------
# .env  (same folder; chmod 600 .env; never commit it)
# ---------------------------------------------------------------------------
# DOMAIN_NAME=example.com
# SUBDOMAIN=n8n                       # → https://n8n.example.com  (create an A record to the server IP)
# GENERIC_TIMEZONE=America/New_York
# SSL_EMAIL=you@example.com           # Let's Encrypt contact
# N8N_VERSION=<current stable tag from n8n release notes, e.g. 2.x.y>
# TRAEFIK_VERSION=<current stable v3 tag>
# N8N_ENCRYPTION_KEY=<output of: openssl rand -hex 32>
#
# Start:    mkdir -p local-files backups && docker compose up -d
# Update:   edit N8N_VERSION, then: docker compose pull && docker compose down && docker compose up -d
# Logs:     docker compose logs -f n8n
#
# Bigger installs: n8n's n8n-hosting repository has a PostgreSQL compose example.
# SQLite (the default above) is fine for a few dozen low-volume workflows.

ZAP INVENTORY — one row per Zap (Google Sheets / Excel). Export the list from Zapier's Zaps page, then fill in by hand.

Columns:
| Zap name | Zapier folder | Owner | On/Off | Trigger app + event | Action steps (apps, in order) | Steps count | Uses Filter/Paths/Formatter/Code? | Uses Zapier-only apps (Tables, Interfaces, Chatbots, Email Parser)? | Tasks last 30 days | Business impact if it fails (Low/Med/High) | Has a premium/partner app? | n8n node exists for every app? (Y/N/HTTP) | Auth type needed (OAuth/API key) | Migration wave (1–4) | n8n workflow name | Parallel-run start | Parallel-run result | Zap turned off on | Notes |

Example rows:
| New Typeform → Sheets row + Slack | Marketing | Ana | On | Typeform: New Entry | Google Sheets: Append; Slack: Send message | 3 | No | No | 120 | Low | No | Y | OAuth (Google, Slack), API key (Typeform) | 1 | MKT – Typeform to Sheets | 2026-10-20 | 120/120 matched | 2026-10-27 | |
| Stripe paid → invoice email + CRM deal | Finance | Sam | On | Stripe: New Payment | Formatter; HubSpot: Update deal; Gmail: Send | 4 | Formatter | No | 85 | High | No | Y | API key (Stripe), OAuth (HubSpot, Gmail) | 3 | FIN – Stripe payment sync | | | | wait for monitoring |
| Daily digest via Zapier Tables | Ops | Lee | On | Schedule | Zapier Tables: Find; Digest | 3 | No | YES | 30 | Med | No | N | — | 4 | | | | | needs redesign: move table to Sheets first |

WAVES (lowest risk first):
  1 = internal-only, Low impact, ≤3 steps, all apps have native n8n nodes (notifications, logging to Sheets)
  2 = Medium impact or uses filters/formatting, still native nodes
  3 = High impact (money, customers, CRM) or webhooks from third parties — migrate only after error alerts work
  4 = uses Zapier-only features or apps with no n8n node → redesign, use HTTP Request node, or keep on Zapier Free

CUTOVER CHECKLIST — per Zap

Before building
[ ] Row filled in the inventory, wave assigned
[ ] Credentials created in n8n (Credentials → Add). For Google/Microsoft OAuth on self-hosted n8n you
    register your own OAuth app and paste the redirect URL n8n shows you — allow 30–60 min the first time.

Build
[ ] Same trigger, same filters, same field mappings (screenshot each Zap step for reference)
[ ] Workflow name = "<TEAM> – <what it does>"; description says which Zap it replaces
[ ] Error handling: an Error Workflow is set in workflow Settings that alerts email/Slack on failure

Parallel run (minimum 7 days or 20 executions, whichever is longer)
[ ] For triggers that can safely run twice: run both, but point n8n's final action at a TEST destination
    (test Slack channel, test sheet tab) and compare outputs daily
[ ] For actions that must not double-fire (payments, customer emails, CRM updates): replay the last
    20 real trigger payloads into n8n with the final step disabled; compare the data each step would send
[ ] Compare counts: Zapier task history vs n8n Executions list — every Zapier run has a matching n8n run
[ ] Field-level diff on at least 5 runs (dates, time zones, number formats, empty fields)

Switch
[ ] Point n8n's final step at production, activate the workflow, turn the Zap OFF in the same minute
[ ] Re-point any third-party webhooks from the Zapier URL to the n8n production webhook URL
[ ] Watch the first 24 h of executions; keep the Zap (off) for 30 days for rollback

After all waves
[ ] Backups proven by a test restore onto a scratch server
[ ] Uptime monitor on https://<your-n8n>/healthz/readiness (returns 200 only when n8n and its database are ready)
[ ] Zapier downgraded to Free (or cancelled) only after 30 days without rollback